Hi Angela,
I have tested to install a web application into an existing virtual
directory. It works fine on my testing machine.
Here are the steps I use:
1. Create a empty directory, e.g. d:\TestVD
2. In IIS, create a Virtual Directory (e.g. named "TestVD") and point it to
the physical directory created in 1, accept all the default settings.
3. Create a ASP.Net application, e.g. named "WebApplication1"
4. Add a Web Setup Project to the current solution, e.g. named "WebSetup1"
5. Add WebApplication1's "Primary output" and "Content Files" to
WebSetup1's Web Application folder
6. Build the solution
7. Double click the WebSetup1.msi package located in the "debug" folder.
8. Input "TestVD" for "Virtual Directory" in the "Select Installation
Address" dialog.
9. Finish the setup.
I can access the WebApplication1 by "http://localhost/TestVD/WebForm1.aspx".
I have also tried to install a WebApplication to a virtual directory that
already contains another one. But I still cannot reproduce your situation.
Could you briefly describe your situation, e.g. any existing files, any
non-default settings, any permission issues and so on? Are you using VS.Net
2002 or VS.Net 2003? If possible, please also give me some steps to
reproduce the situation.
Should you have any concerns or new findings regarding this issue, please
feel free to let me know. I look forward to hearing from you.
Regards,
Felix Wang
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.