Quantcast
Channel: MSBuild forum
Viewing all articles
Browse latest Browse all 2763

Upgrading .Net 3.5, Visual Studio 2008 to .Net 4.0, 2013 generates lots of run time errors

$
0
0

I am having several issues since I upgraded my .Net App built with Visual studio 2008. I upgraded my app because I would like to take advantage of the functionalities in .Net 4.0 and later. I have been getting a lot of errors which for the most part are thrown from visual studio designer generated code such as DataSets, Linq to SQL, Cryptography etc. The errors I get are usually different but I have noticed that they are mostly related to the mismatch between 32 bit and 64 bit .Net framework types (I am now using Win 7, Visual Studio 2013, 64 bit). I usually get "System.AccessViolationException occurred in mscorlib.dll", managed Debugging Assistant "FatalExceptionEngineError" error messages. often times I get the error telling me that the System.Windows.forms.pdb or mscorlib.pdb files were not found or failed to load or something similar I have read all the documentation on migrating my app and have tried all the reasonably related suggestions, but nothing seems to work and this issue is now getting into my bones. I followed one suggestion in one of these threads where it was suggested to delete the .suo file and restart VS, when I did, I now get this error message when I build:

"Error 1 Could not run the "GenerateResource" task because MSBuild could not create or connect to a task host with runtime "CLR2" and architecture "x86".  Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "C:\Program Files (x86)\MSBuild\12.0\bin\MSBuildTaskHost.exe" exists and can be run..." I also get this:

"Error 2The "GenerateResource" task's outputs could not be retrieved from the "FilesWritten" parameter. Object does not match target type..."


What would you suggest? Is there anything I am missing? I do not wish to migrate my app to run on 64 bit systems, It works fine on compatibility mode and would prefer to keep it that way, but I would definitely like to take advantage of the newer .Net Framework functionalities without breaking my app. 


Viewing all articles
Browse latest Browse all 2763

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>