'Could not load file or assembly 'Telerik.Web.UI, Version=2024.3.805.462, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. Invalid pointer (Exception from HRESULT: 0x80004003 (E_POINTER))'
Please make sure that the targetFramework of the app matches the .NET version of the Telerik Web UI assemblies. If the app is built against .NET 4.0, use the Telerik assemblies built for .NET 4.0 (in the manual installation they reside inside the Bin40 folder, for NET 4.5 and above, use the assemblies in the Bin45 folder). One way to test if this is the cause of the issue is to double-click on the error in the Visual Studio Output window which will open the file with the error. Upon opening the file, Visual Studio will then do some thinking and then the error will disappear.
Other steps to resolve the issue:
Open the file and Delete the contents of the license.licx and make it read-only.
Alternatively, you can also delete the whole license.licx file and rebuild the solution
Or right-click the Telerik.Web.UI.dll file in Windows Explorer, select Properties, and then click the 'Unblock' button on the General tab near the bottom.
Or if your app is under the source control to make it ignore the license file so any changes on a developer machine won't make it into the build machine or anywhere elsewhere.
A customer report indicates that if the reference errors persist after following the steps above, the solution is to re-install the NuGet package microsoft.bcl.build.
If the above suggestions do not help:
remove the reference to Telerik.Web.UI.dll in Visual Studio and re-add it.
Hi Bj,
The error is discussed in the How To Fix License File Related Errors article:
Please make sure that the targetFramework of the app matches the .NET version of the Telerik Web UI assemblies. If the app is built against .NET 4.0, use the Telerik assemblies built for .NET 4.0 (in the manual installation they reside inside the Bin40 folder, for NET 4.5 and above, use the assemblies in the Bin45 folder). One way to test if this is the cause of the issue is to double-click on the error in the Visual Studio Output window which will open the file with the error. Upon opening the file, Visual Studio will then do some thinking and then the error will disappear.
Other steps to resolve the issue:
If the above suggestions do not help:
Regards,
Vasko
Progress Telerik