when I try to obfuscate a dll developed with Visual Studio, I get this error message:
An error occurred during processing:
Failed to get type definitions for CreoParamLm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f4e4fd84ef410cf6
Cannot clean pool
I didn't find any info searching with Google for this typology of error, do you have any idea?
Thanks in advance.
Related
I have updated my xamarin.ios project to IOS14 SDK and i am getting the following build error
Error MT2002: Failed to resolve assembly: 'Microsoft.WindowsAzure.MobileServices.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' (MT2002)
I understand that the Azure Mobile Services Library is deprecated, however is there a way that i can build my project without migrating to Azure Mobile Apps?
#September 2021 Update
With Xamarin.iOS 14.20.0.24 i continue to have the error
I recently updated my visual studio to 2017 Enterprise.
I used to use DevExpress v15.1
Today, I upgraded my DevExpress to version 18.1 and when I build my .Net MVC5 Application Solution, I got the following error
The type 'XtraReport' is defined in an assembly that is not
referenced. You must add a reference to assembly
'DevExpress.XtraReports.v15.1, Version=15.1.8.0, Culture=neutral,
PublicKeyToken=b88d1754d700e49a'.
The above Error is located in ReportController.cs
I checked my references Folder under the project to find that the DevExpress.XtraReports.v18.1 is there.
What might be the cause of this error?.
Thank you for your help.
Based from the message, the XtraReport still references the older version of its DLL assembly:
'DevExpress.XtraReports.v15.1, Version=15.1.8.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a'
Usually this problem occurred because Project Converter failed to update XtraReport related references after upgrade. In this case, you can manually remove all references to older assemblies (version 15.1) and then add references to new assemblies (version 18.1).
Also make sure that web.config file has these assembly information like below example (X indicates revision number):
<add assembly="DevExpress.XtraReports.v18.1, Version=18.1.X.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a" />
<add assembly="DevExpress.XtraReports.v18.1.Web, Version=18.1.X.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a" />
If the solution above failed, try install the assemblies to the Global Assembly Cache (GAC) by navigating to X:\Windows\assembly (X stands for the system drive letter) and copy all new DevExpress assemblies to that folder (including DevExpress.XtraReports.v18.1), as mentioned in this issue.
Related issues:
Errors after upgrading DevExpress version
DevExpress.XtraReports.UI.XtraReport is not defined after upgrade
The type 'DevExpress.XtraReports.UI.XtraReport' is defined in an assembly that is not referenced
When I try to build a hello-world VB.NET project with MSBuild enabled in Monodevelop I get this error.
'Error: Target named 'Build' not found in the project. (HelloWorld)'
The project will build when the MSBuild feature is disabled. I don't really know what I'm doing, but I'm trying to set myself up so I can start writing .NET applications. I'm not entirely sure I need this feature, so maybe someone can enlighten me as to what MSBuild is used for. Thanks.
OK so there are a few MonoDevelop bugs here due to support for VB.NET not being as good as the C# support.
First MonoDevelop does not add the <Import Project="$(MSBuildBinPath)\Microsoft.VisualBasic.targets" /> to the .vbproj file.
This is filed as bug 554445
If you add this import to the .vbproj the error about the missing 'Build' targets should be fixed. However then you will probably run into the next problem.
Mono's MSBuild then tries to use vbnc.exe which does not seem to currently be shipped with Mono.
If you try to use the vbc.exe instead by setting the VbToolExe to be vbc.exe in the project:
<VbcToolExe>vbnc.exe</VbcToolExe>
You then run into another exception.
System.TypeInitializationException: The type initializer for 'Microsoft.CodeAnalysis.VisualBasic.VisualBasicCommandLineParser' threw an exception. ---> System.TypeLoadException: Could not resolve type with token 01000286 (from typeref, class/assembly Roslyn.Utilities.IObjectReadable, Microsoft.CodeAnalysis, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
There is another bug logged for this but it is a private bug so you cannot see it.
So currently VB.NET projects do not compile with MSBuild so you will either need to use xbuild or the default built-in support for using vbc.exe in MonoDevelop.
I am using VS 2017 with version 15.3.0. I have a project with C++ source codes that can be built successfully in VS version 15.2 but failed in 15.3 with the following error:
msxml2.lib(msxml2_i.obj) : fatal error LNK1103: debugging information corrupt; recompile module
Does anyone have suggestions about this?
I have filed a bug report to Microsoft including a sample application which reproduces the bug:
https://developercommunity.visualstudio.com/content/problem/99785/mfcs140libstdafxobj-fatal-error-lnk1103-debugging.html
Hopefully this will be fixed in a subsequent 15.3.x update.
I met the same problem when my project use an external lib(CyAPI.lib).
I tried delete the Debug folder, and recompiled, but the problem still exist.
I resolved the problem by changed to CyAPI.lib to the newest version.
I'm attempting to load a pre-existing Umbraco CMS site into a Visual Studio project and am caught up in a bit of DLL hell.
Here is the error message I get when attempting to compile the site:
Could not load types from assembly Umbraco.Core, Version=1.0.5462.37503, Culture=neutral, PublicKeyToken=null, errors:
Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
File name: 'Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'
I've attempted to re-install Newtonsoft from NuGet, re-install Umbraco from NuGet, delete all DLLs and re-install, removed the Newtonsoft dependentAssembly, every possible solution I've been able to find and this error continues to come up.
Any suggestions?
I'm guessing the binding redirect isn't set up correctly in the web.config file. Try running this in the nuget package manager console:
PM> Get-Project –All | Add-BindingRedirect
This ended up being a bit of a misunderstanding on my part from following the Umbraco videos. I was attempting to set up a new Visual Studio project, import all the DLLs needed, and then move the site content into the project.
All I really needed to do was create a blank project, then move the site content, with all of its DLLs, into the project. This let me immediately start editing the project.
The best solution was to install an earlier version of the package and then upgrade.