visual studio .net debugging: I'm getting "compiler failed with error code 2000" intermittently when
attempting to debug a solution. The error message details indicate that the
compiler is trying to find a dll (which one in particular varies) in a
Temporary ASP.NET folder that does not exist. Generally speaking, the
solution works the first time I compile it, but after making one or more
changes to the codebase (even adding a comment) I will begin to get this
error, at which point I need to restart VS.NET to get things working again.


I've searched high and low for this problem, and have found only two pieces
of advice so far:


a) reinstall IIS and VS.NET
b) switch from debug to release mode, and try again.


I've done a) with no luck. B) seems like a pretty poor work-around.


Is there a hotfix for VS.NET to fix this problem?

Hello,
Thanks for posting in the group.
I have reviewed your thread and currently I am finding somebody who could
help you on it. We will post back in this newsgroup as soon as possible.
If there is anything unclear, please feel free to post in this group and we
will follow up here.

Thanks and regards,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties and confers no rights.

[quoted text, click to view]

We are using VS.NET 2003


[quoted text, click to view]

If there are strong-named assemblies involved, they must be third-party,
since we haven't strong-named anything ourselves on this project. I'll have
the developer is question look into the third-party components, to see how

Hi Mercatus,

As for the "compiler failed with error code 2000" error when executing
ASP.NET application, based on my experience, there're two possible common
causes:

1. What's your IDE's version, are you using the VB.NET 2002? If so, there
is a known issue on this which require a hotfix to resolve it.

2. If you're using the 2003 version of VS.NET, I think it's likely that the
problem is caused by strong-named assmelies version mismatch after we
recompiled the assembly from IDE. So is there any custom components or
controls (be referenced in your asp.net project) which are strong-named or
is your ASP.NET web project's assembly be compiled as strong-named?

If so, we need to add all the strong-named assembly into GAC at runtime( do
not put strong-named assemlbly in asp.net web application's private bin
folder) since ASP.NET dosn't support strong-named assembly in private bin
dir.

Please have a check to see whether this is the cause. Hope helps.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Hi Michael,

[quoted text, click to view]

It's alright, just like what Steven figured out, it is better for your
developers to check all the assembles which belong to the ASPNET project or
it referenced, make sure the assembly will be put into the GAC if it is
strong named.


Thanks and looking forward to hearing from you.

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.