 |
Something Odd... A Resolution to a Problem...
[reply]
|
05/18/04 11:08 AM EST
posted by JER email web |
|
For the past 32 hours I've been unable to edit web projects in Visual Studio 2003 .NET v1.1 on Windows XP. The exact error was "Unable to open Web project 'MyProject'. The file path 'C:\Inetpub\wwwroot\MyProject' does not correspond to the URL 'http://localhost/MyProject'. The two need to map to the same server location."
I've had that error before when I've changed the default web root or if a virtual directory hasn't been created. This time, however, I couldn't even create NEW web projects!!!
After much fiddling with Visual Studio & IIS, I finally opted out and handed it off to Jake. He was able to fix my problem by doing the following. It is unclear which steps were involved in actually fixing the problem, but by combining these steps, he got it working:
- Repairing Visual Studio installation from install disc (mostly registry changes, I believe).
- Reinstalling IIS.
- Reinstalling .NET Framework version 1.1.
- Re-registering .NET Framework with IIS via aspnet_regiis.exe
|
|
[reply]
|
05/18/04 05:30 PM EST
posted by nate web |
|
| Any idea what caused the problem in the first place? Did you run a patch just prior to the glitch? |
|
|
|
I really don't know what could have happened. I ran Visual Studio all day Friday, turned off my machine, and when I turned it on the following Monday, I had issues.
I was experiencing some battery issues last week, so maybe I shut down improperly or pulled the plug while my machine was making changes to IIS settings??? |
|
[reply]
|
05/19/04 01:50 PM EST
posted by Jake |
|
The problem was a couple fold:
1.) the registry was corrupt, primarily the registration of .csproj to the IIS MIME type extension which passed to VS.NET
2.) VS.NET attempts to open web projects using IE to send the project to VS.NET. If the registration in IIS is wrong, then VS.NET will not open the project
3.) The .NET framework was not registered correctly with IIS. IIS Forgot how to open .NET files: it passed the pages to the JIT Compiler b/c thats built into the kernel (JIT is a function of Windows, NOT IIS) so thats why the pages rendered. But when VS.NET Attempted to open a project file OR a cs file from IIS, IIS was like, hey WTF? I can compile it, but I dont know what the f*** to do besides that? IIS was like "Whats VS.NET? F*** off IE! Come back when you want some ASP Pages"
4.) The ISAPI filters section of IIS , which allows permissions delegation and editing of files from IE was gone, so that had to be fixed also.
Why did this all happen. Because Jerry is a bad person and God does not like him. |
|
|
|
Knowing Windows, IIS, .NET and VS.NET fairly well myself, the summary that I can take from the above posts and resulting comments is as follows:
Jerry tried some stuff to get it working and couldn't so he handed it off to Jake who basically just did what all windows people do, he re-installed and re-registered a whole bunch of crap and once it was working came up with some reasoning for why it probably didn't work before.
I will bet just running aspnet_regiis.exe -i would have probably have done the trick, but we may never know...
Well played Robs, well played. |
|
|
|
| Ha. The first thing I DID was run "aspnet_regiis.exe -i" & didn't solve a thing. I'm more surprised that this seems to have been an IIS problem, not a Visual Studio problem. |
|
Note: Only registered ShinyDonkey.com users
can post images. Only administrators can delete images.
New messages disabled indefinitely due to SPAM.