Configure an IIS Virtual Directory with Server Extensions ..

I am about to pull all my hair out. I have spent hours trying to
figure out how to configure the necessary server extensions on a
virtual directory in IIS so I can wrap an Interdev project around it.

Environment: XP Pro SP1, IIS 5, FP2000 extensions, Interdev 6

I was given the source for an existing production website, which for
space reasons needs to be on a different physical drive from my default
web (which is located at c:\inetpub\wwwroot). I created a virtual
directory using the IIS console pointing to the d:\web folder. I then
tried to create a new project in Interdev that pointed to the virtual
directory - but Interdev didn't show it in the existing web sites
dropdown. I went back to IIS console and tried to configure server
extensions on the virtual directory, which seemed to work (no errors),
but it didn't seem to do anything, either.

I read in some other posts that you can't configure server extensions
on a virtual directory whose physical path is outside the local web or
that FP extensions can't see the virtual directory, but I don't buy it.
Interdev itself is able to do the same thing!

The My Documents folder on this machine is pointed to the D: drive.
When I go into Interdev and create a scratch "local" project called
Project1, it creates a web application called Project1 under
c:\inetpub\wwwroot\Project1. It also creates a separate folder for the
"local" application under My Documents\Visual Studio
Projects\Project1\Project1_Local. Remember, this local folder is on
the D: drive. When I press F5 to run the application within Interdev,
it magically creates a virtual directory under
c:\inetpub\wwwroot\Project1_Local and it has all the necessary server
extensions to communicate with Interdev. How is this possible? And
how is this different from what I'm trying to do? I want to configure
server extensions on d:\web, and then create a virtual directory in IIS
to run it.

This should be easy and it is a big waste of time - thanks Microsoft.

If anyone has run into this problem and solved it, I would be grateful
for your help. I need all the hair I have left.

Thanks

: This should be easy and it is a big waste of time - thanks Microsoft.

Let's have a look at the situation before jumping to conclusions:

: went back to IIS console and tried to configure server
: extensions on the virtual directory

Best to configure your extensions for the website.

Next, in Interdev, connect to the website first, and then your existing
application should be listed in the drop down. After choosing this, Interdev
will create a local copy of the project in your My Documents folder.

If your application is not listed in the drop down, ensure that your virtual
directory is marked as an application root (not just a virtual directory) in
IIS Manager. Application roots look like a globe in a box. Virtual
directories alone look like a folder with a globe.

Cheers
Ken



<svierregger.TakeThisOut@gmail.com> wrote in message
news:1141429803.692311.285970@p10g2000cwp.googlegroups.com...
:I am about to pull all my hair out. I have spent hours trying to
: figure out how to configure the necessary server extensions on a
: virtual directory in IIS so I can wrap an Interdev project around it.
:
: Environment: XP Pro SP1, IIS 5, FP2000 extensions, Interdev 6
:
: I was given the source for an existing production website, which for
: space reasons needs to be on a different physical drive from my default
: web (which is located at c:\inetpub\wwwroot). I created a virtual
: directory using the IIS console pointing to the d:\web folder. I then
: tried to create a new project in Interdev that pointed to the virtual
: directory - but Interdev didn't show it in the existing web sites
: dropdown. I went back to IIS console and tried to configure server
: extensions on the virtual directory, which seemed to work (no errors),
: but it didn't seem to do anything, either.
:
: I read in some other posts that you can't configure server extensions
: on a virtual directory whose physical path is outside the local web or
: that FP extensions can't see the virtual directory, but I don't buy it.
: Interdev itself is able to do the same thing!
:
: The My Documents folder on this machine is pointed to the D: drive.
: When I go into Interdev and create a scratch "local" project called
: Project1, it creates a web application called Project1 under
: c:\inetpub\wwwroot\Project1. It also creates a separate folder for the
: "local" application under My Documents\Visual Studio
: Projects\Project1\Project1_Local. Remember, this local folder is on
: the D: drive. When I press F5 to run the application within Interdev,
: it magically creates a virtual directory under
: c:\inetpub\wwwroot\Project1_Local and it has all the necessary server
: extensions to communicate with Interdev. How is this possible? And
: how is this different from what I'm trying to do? I want to configure
: server extensions on d:\web, and then create a virtual directory in IIS
: to run it.
:
: This should be easy and it is a big waste of time - thanks Microsoft.
:
: If anyone has run into this problem and solved it, I would be grateful
: for your help. I need all the hair I have left.
:
: Thanks
: