Last post Jul 20, 2009 03:45 AM by XIII
Jul 19, 2009 02:38 AM|Dickow|LINK
I'm using VS 2002 to work on some old ASP.NET 1.1 sites. These have been functioning in production for years, but now, suddenly, my compiles run on the sites result in non-functioning sites. They crash with this error:
An unhandled exception occurred during compilation using the CodeDomProvider 'Microsoft.CSharp.CSharpCodeProvider'. Please review the stack trace for more information about the error and where it originated in the code.
I'm in a time crunch to fix this now. Any suggestions before I go into panic mode?
Jul 19, 2009 03:22 AM|XIII|LINK
did you use VS2002 to open a 1.1 solution and then you get the error? If so the problem's obvious: VS2002 was made to target 1.0 while
VS2003 was put in place to work with 1.1 solutions. You need to change your Visual studio environment in order to properly open en compile it.
Jul 19, 2009 05:14 PM|Dickow|LINK
This is helpful I'd say, since changing the IIS settings for these sites to version APS.NET 1.0 did change things, but there must be more to it than that. After resetting the ASP.NET version in IIS for each web app at least now I get an "Server Application
Unavailable" in my browser instead of the usual unhandled exception error page. So, something got in there maybe and set all those version settings to 1.1 instead of 1.0, or something? It had been fine for about 5 years or so. I didn't change anything. As
far as I know, I have been gleefully working very successfully with 1.1 and VS 2002 for about 5 or 6 years or whatever. I moved up to 1.1 as soon as it became available.
Anyway, something is still very haywire, because I still can't successfully compile any of those old web apps under VS 2002. Now they all fail with "could not instantiate the resource processor" error messages during the compile. I can't compile any of them.
Maybe I need to do a repair or reinstall of VS 2002. It's seriously bunged it seems. I'm heading toward blaming MS update, because the machine in question is rarely used except as a development server, and only after the MS Update during the past week did
I first notice this problem.
Jul 20, 2009 03:45 AM|XIII|LINK
for an 1.1 application you need VS2003, not 2002. Also perhaps if you reinstalled your visual studio 2003, did you also install the hotfixes and service packs like you did back then?