Hi!

We have about 16 web projects accessed through network that are not in wwwroot and cross reference each other. Following are steps of how to add a project into solution (as far as I remember - did not added new proect so far):

1. Configure FrontPage extensions for web site
2. Create required folder and configure it as new FrontPage extentions folder.
3. In the .NET studio options, set web project access mode to use FrontPage.
4. Create web project, when creating it, specify path to the folder you prepared.
5. Close solution
6. In the .NET studio options, set web project access mode to use file system.
7. Remove FrontPage from project's directory (be sure to do not clear out the entire directory!)
8. Open solution. If it has no access to //mashine/wwwroot$, it should ask you for network path to the project. Type it (it is required only once - stored in solution file), ok.

When you have existing web project, in step 4. just add it as web project. However, it does not always works (using framework 1.0), in certain cases I had to re-create project file.

Just keep in mind that you should create web project as WEB project on WEB server first. Then access it as you wish :-)

Also, just for running of project from subfolder you do not need to do anything in .NET framework. For running web site from subfolder, just place all web site files and folders into required subfolder (include web.config, global.asax files, bin fodler etc.). Then configure that folder under IIS manager as Web application.

You can re-use copy of that solution file on all network machines. We use solution file placed in the shared folder on the web server machine. There are nusiances though - solution stores not only projects, but also what windows were last opened by user, so there are certain inconveniences in this. There are few issues on the 1.0 version of framework. In general, it works ok and we're very happy with ability to split one large we site to 16 different projects in different subfolders.


>Setting up a virtual directory seems like a good solution. However, I am not able to choose any directories off the network drive. The OK button becomes disabled.
>
>Is there a security issue that I can get around? Or will IIS not allow a virtual directory with a source folder from a network drive?