Last post Jul 26, 2010 11:21 AM by joeastral
Jul 20, 2010 02:00 PM|joeastral|LINK
I installed Visual Studio 2003 on my XP Pro box so I could add a quick feature to a 1.1 coded application. All our other apps are in 2.0 but the customer doesn't want to upgrade this one. But even when I build a blank solution and try to debug it, all
I get is a blank page loading. Not even an error message in the event log or in .NET. If I pause in .NET it stills says it's in the managed assemblies or such and hasn't gotten to my code behind yet. I've insured the proper NTFS (ASPNET, IUSR*, IWAM*) access
to the virtual folder directory. The framework version in IIS is set to 1.1. I've tried uninstalling and reinstalling both 1.1 and 2.0 .NET IIS controls (aspnet_regiis). I checked the IIS logs and it shows that the page request is being sent even though
it's not being returned successfully (or hanging in this case.)
I know the obvious answer is to just convince the client to upgrade their application to ASP.NET 2.0 but any idea what would cause VS2003 1.1 web apps not to run in this instance? Am I missing permissions, or is it broken front page extensions, or some
other recommendation for getting a better error message? Thanks!
visual studio 2003
Jul 26, 2010 11:21 AM|joeastral|LINK
Never figured this one out. Had to setup another machine that just had VS2003.