visual studio 2012 - Latest Resharper giving me random build errors -
For a week now, I'm getting random build errors that do not understand at all. First of all, I released another build until there was no error.
-
error MSB3249: application configuration file "now" App.config "is invalid file 'XXX \ app.config' not found.
The strange thing about this one is that XXX does not have any app.config (this is a native C ++ dll) in the asociated project. Also, XXX optional projects.
Error MSB3027: Could not copy "YYY.dll" to "bin \ x86 \ Debug \ YYY.dll" The number of re-withdrawal of 10 is exceeded. : \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ Microsoft.Common.Targets (3540,5): Error MSB3021: Unable to copy the file "YYYdll" with "bin \ x86 \ Debug \ YYY.dll" This process can not use the 'YYY.dll' file because it is being used by another process .
They always come in pairs, looking at the process with Explorer, that the other process is always MSBuild.exe or devenv.exe.Data.
Some projects could not be loaded. I made a copy of the error message to copy it Tried to reproduce but the frequency is very low.
Deadlock / Starvation: Build gets stuck in the "Create Startup" line and let me cancel it. When I do this, then some of the previous errors are visible.
My environment: Windows 8.1 64bit, Visual Studio 2012, Reservoir 8.2, 98 Solutions with Projects (C #, VB.NET, C ++ / CLI and C ++)
I tried to rebuild, clean, open and close, restart windows, disable reshers and try to restart VS. Errors went with this last fix but I missed the Nifty R # stuff. I look at R # issue tracker, but did anyone else experience this? R #? Disabled
Rescars recently changed the way to resolve the reference - it is now using MSBield To solve some things, there are several things that you can try instead of Core Visual Studio:
- Install the latest version (RC was released today, April 25, Fixes many issues related to the creation of errors)
- Go to ReSharper, Options, Normal, and Ni Try to rebuild C,
Use msbuild to get project contexts option, then rebuild.
If the latter resolves your problem, then I recommend That you open a problem, so that they can fix it.
Hope that helps!
Comments
Post a Comment