"Error 5 A problem occurred while trying to set the "Sources" parameter for the IDE's in-process compiler. Attempted to read or write protected memory. This is often an indication that other memory is corrupt. "
what is the problem ?
thanks for helps
Does this only happen on one machine? Does it happen for any projects, or just those two projects? Can you identify anything special about them?
Dan
--Rajeev
This is a strange error and we'd like to know more about it in case it's a bug. Could you tell us more about your situation? Are you developing in Visual Basic or C#? Does this problem seem related to your unit tests? Are you generating any code files as part of your build or design time process? Can you try these two things, and let us know the results:
1) Build from the command line. To do this, open a "Visual Studio 2005 Command Prompt" (found under the Visual Studio 2005 folder on your start menu), browse to the folder containing the solution or project that you're building and run "msbuild.exe <solution/project filename>". Does this produce errors? Are they the same errors?
2) Get a diagnostic log from inside Visual Studio. To do this, open your solution in Visual Studio and select the "Tools/Options..." menu item. Select "Projects and Solutions" and "Build and Run" from the tree on the left, and there should be a combo box for MSBuild Output Verbosity. Select "Diagnostic" from this combo box and hit apply/ok. Now repeat the build that reproduces the error, and copy the contents of the Output window. If you could post those here, that could help us diagnose the problem.
Thanks for reporting this problem, hopefully we can figure out what's going on.
jeff
I'm having the same problem. Unfortunately it's sporadic and unreproducable, but I have the IDE open right at this moment and producing the same error.
It happens for me when I hit f5 on my unit test project. This is on the (trial) release version of VS 2005 Team Suite.
1. The build from command line succeeds. If I close the IDE and recompile it also works. Just before the error I was tracing it fine, then suddenly it didn't work despite making no code changes.
2. I have captured the content from doing this. It is unfortunately long (811 pages in word) so I will email it to your ms address.
Cheers
