K
kevin.koehne
I'm having a problem building a solution in VS2003 (.NET 1.1) on
Windows XP. I get the error:
"Unable to open Web project 'projname'. The file path
'C:\app-1.6.0.600\solution\projname' does not correspond to the URL
'http://localhost/projname'. The two need to map to the same server
location."
What is frustrating me is that the error message is technically
correct; that particular URL is not pointing at that specific system
path. In IIS manager, the virtual directory "projname" is pointing at a
folder called :C:\app-1.7.0.602\solution\projname".
Just as an FYI, the way that we are doing our builds, is that for every
release, we create a new folder named with the version number and then
repoint all of the virtual directories to the new folders. It appears
that the solution doesn't realize that the virtual directory points at
a new folder - but there doesn't seem to be any file in which the old
folder name is stored.
This process has been working for the last 1 1/2 years and the only
change to the server that I am aware of is that we've installed .NET
2.0 on the machine in order to run the new SQL Server 2005 Manager.
Any help in figuring out what is going on would be appreciated.
Thanks,
Kevin Koehne
Windows XP. I get the error:
"Unable to open Web project 'projname'. The file path
'C:\app-1.6.0.600\solution\projname' does not correspond to the URL
'http://localhost/projname'. The two need to map to the same server
location."
What is frustrating me is that the error message is technically
correct; that particular URL is not pointing at that specific system
path. In IIS manager, the virtual directory "projname" is pointing at a
folder called :C:\app-1.7.0.602\solution\projname".
Just as an FYI, the way that we are doing our builds, is that for every
release, we create a new folder named with the version number and then
repoint all of the virtual directories to the new folders. It appears
that the solution doesn't realize that the virtual directory points at
a new folder - but there doesn't seem to be any file in which the old
folder name is stored.
This process has been working for the last 1 1/2 years and the only
change to the server that I am aware of is that we've installed .NET
2.0 on the machine in order to run the new SQL Server 2005 Manager.
Any help in figuring out what is going on would be appreciated.
Thanks,
Kevin Koehne