Hi there,
I'm facing a problem that is driving me nuts. The scenario is as follows:
1) Create an empty directory structure e.g. C:\Dev1\TestWeb App
2) Map a virtual directory e.g. TestWebApp to this new directory
3) Under C:\Dev1 create a blank visual studio solution and add a new web
project called TestWebApp (which will be created in C:\Dev1\TestWeb App and
mapped to http://localhost/TestWebApp)
4) Everything runs smoothly, visual studio maps the url that you created in
1) to new web project created in 2). The web app can be accessed at
http://localhost/TestWebApp
5) Check all this into SourceSafe
6) Go to a clean machine and get the project created in 4) to anywhere, say
C:\Dev2\TestWeb App
7) On the clean machine, create a new virtual directory mapping for
TestWebApp to C:\Dev2\TestWeb App
8) If you try to open the solution now on this new machine, even with the
virtual directory mapped, visual studio prompts you to set the project
location and defaults the working directory to something like
http://localhost/TestWebApp_1 which it creates under inetput\wwwroot
This will not work for me - I'm trying to automate my build process by
calling devenv.exe and hence need to be able to set the virtual directory to
whatever I want.
Has anyone experienced this problem and found a solution?
Regards,
Danny
