visual studio problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

scottrm - 26 May 2006 14:54 GMT

I am using Visual Studio .Net 2003 on Windows Server 2003 SP1 to develop a
web application, I seem to be experiencing intermitent problems where I get
an error message saying

Unable to open Web project "MyApp". The file path
"c:\Inetpub\wwwroot\MyApp" does not correspond to the URL
http://Localhost:/MyApp. The two need to map to the same server location.
HTTP Error 500: Internal Server Error.

However IIS is mapped to the correct directory and I checked the webinfo
file and it is correct as well. Any ideas?

Any ideas?

Thanks

Signature

Scott

Reply to this Message

scottrm - 26 May 2006 15:25 GMT

to add to this a little, I have already tried deleting the temp and
vswebcahe, re-staring IIS and re-creating the virtual directories, none of
which seems to work

The entry in the solution fiel for the urlpath also seems to be correct

Signature

Scott

> I am using Visual Studio .Net 2003 on Windows Server 2003 SP1 to develop a
> web application, I seem to be experiencing intermitent problems where I get
[quoted text clipped - 11 lines]
>
> Thanks

Reply to this Message

Steven Cheng[MSFT] - 29 May 2006 11:26 GMT

Hello Scott,

Thank you for posting.

From your description, you have an ASP.NET 1.1 web project(built with vs
2003), currently you found that the vs 2003 IDE is unable to open the
project in IIS, correct?

Based on my experience, there are several things which may cause such error
behavior:

1. The IIS website or application virtual directory's configuration has
been changed

2. the web project's project file has been corrupted.

I suggest you first check whether the issue is specific to that project.
You can try creating and open web project on that error project's IIS site,
if that works well, we can isolate the issue to that project only.

Then, generally, we can copy the project to another place and then remove
it completely from IIS. After that, use VS 2003 to recreate the project
with the same name and same virtual path in the same IIS site and copy all
the web project contents from orignial project into the new created project.

Hope this helps.

Regards,

Steven Cheng
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================

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

Signature

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

Reply to this Message

scottrm - 30 May 2006 09:30 GMT

Thanks for your reply, this may fix the problem but it doesn't seem to stop
it occurring and the problem is occurring repeatedly and it is too time
consuming to have to fix it like this every time. Any idea how to prevent the
problem in the first place.

Signature

Scott

> Hello Scott,
>
[quoted text clipped - 40 lines]
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)

Reply to this Message

Steven Cheng[MSFT] - 31 May 2006 09:08 GMT

Thanks for your response Scott,

If so, we'd still focus on the two parts:

the IIS server

and the project itself. Is there any changes in the IIS or the virtual
directory when the problem reoccurs? Or is there any changes in the project
file? As for project file you can keep a copy of the project file(which can
work) and whe the problem occur, compare the problem project file with the
original copied one.

Regards,

Steven Cheng
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================

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

Signature

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

Reply to this Message

Rate this thread:

visual studio problem

Free Magazines