I had more or less the same problem.
My solution (crude but it works) is to create a web application
project on my local machine (with IIS installed) and copy those files
to my webserver. Then I edited the project files itself to make sure
all the paths were correct.. This way I don't need a virtual directory
and VS.Net thinks I did everything by the book.
This principle also works when you want to run websites on different
ports (say 81).
Q
[quoted text, click to view] On 25 May 2004 05:58:13 -0700, jhoge123@yahoo.com (John Hoge) wrote:
>I'm moving some intranet applications from asp to vs.net, and I am
>wondering why VS insists on using a virtual directory. Most of my apps
>are in local websites with their own IP and domain.
>
>Is there a way to create a website in IIS that points to a specific
>directory and then build a VS project in the root of that directory?
>In other words, say site.domain.com points to e:\mysite, I would like
>to build a VS application in e:\mysite instead of
>e:\mysite\myapplication1 or some such virtual directory that VS
>insists on creating. Seems simple, right?