Recently upgraded to VS 2005. With a large project, I keep getting this message when I try and build.

Looked through the forums - have tried cleaning and rebuilding - no joy.

Have also tried increasing size of virtual memory - no joy.

Any ideas?

Thanks

Tim,

Many thanks for the info.

I spoke to Support. They need the KB number in order to supply me with the hot fix.

Many thanks

There is not a KB for this yet.  You are the first customer asking for the fix.  So, it will require support to submit a Quick Fix Engineering (QFE) request.  I'm not sure what red-tape is involved -- but once it gets to me I'll make the fix and they will issue a KB.  Feel free to tell them I sent you.

Make that two people.  I am getting the same error.

I was half-way through a project and it was going fine and then this error appeared out of no where.  I work for a large organisation and we're looking to move from VS2003 to VS2005 but this kind of error worries me and perhaps we shouldn't move over until at least SP1 or SP2.
 

Matt, SP1 is now out.  I don't know if it specifically addresses this issue; but if you find after installing SP1 this issue no longer occurs, please post back so other people may know.

Visual Studio 2005 SP1 information
http://support.microsoft.com/?kbid=928957

Visual Studio 2005 Standard, Professional, Team Editions SP1 download:
http://www.microsoft.com/downloads/details.aspx?familyid=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en

Visual C#/J#/C++/Basic/Web-Dev 2005 Express SP1 downloads
http://www.microsoft.com/downloads/details.aspx?familyid=7B0B0339-613A-46E6-AB4D-080D4D4A8C4E&displaylang=en

Visual Studio 2005 Team Foundation Server SP1 download:
http://www.microsoft.com/downloads/details.aspx?familyid=A9AB638C-04D2-4AEE-8AE8-9F00DD454AB8&displaylang=en

I'm using VS2005 Team Edition for Developers with SP1 installed.

I've had this problem 3 times today. If I press F5 again the build succeeds. As the app gets bigger this could become annoying but I can live with it at the moment

This problem has NOT been fixed by SP1.  I still get this daily.  As a matter of fact, I got it 3 times today.  Keep in mind, this happens with a very large solution.  The first time I got it today, my entire machine locked up.  Could not even click "Send Error Report", had to hard boot.

Can somebody give me an idea when this is going to be fixed?  I don't have to work with this solution all the time, but still this is quite annoying.  Especially when the build time is like 60 seconds before it gives me this error.

 I just know this problem today. And I follow your suggestion to press F5. It works fine. Thank you very much.

Peter Ritchie:

There is nothing publicly announced to suggest there will be a service pack 2 for Visual Studio 2005.  You might want to download the Orcas Beta 1 to see if it does not have this problem.

I'm running Visual Studio Team System 2008 Beta 2 and this problem still exists.

Try closing visual studio, deleting all your obj folders from the projects in your sln, opening your sln, F5.  That fixed it for me when I had this issue.

Nevermind - that only seemed to temporarily fix the problem.  Doing a Clean on the sln may have fixed it, though.

This thread is over 6 months old!  May I ask why you decided to resurrect it?!

Just had the issue myself and was looking to deal with it.  Didn't check out the date.  My bad.

JoshStodola:

This thread is over 6 months old!  May I ask why you decided to resurrect it?!

Why not? Obviously the issue is still occurring even with up and coming Visual Studio 2008. I'm not sure why someone would want to open another thread on the exact same topic when there is already discussion around it in this thread, which is still unresolved.

I had an update to SP1 a couple days later and the problem was fixed.  Run Windows update.

Best regards...

Do you have the KB Article # for the update? I've run every Windows Update that's been offered, and although Visual Studio 2005 did eventually stop showing this behavior. Visual Studio 2008 is showing it again. Perhaps if I had the KB # for the update I could reference that with Microsoft and burn one of the MSDN support incidents to get a patch created for 2008.