Configuring (enabling) Front Page Extensions for IIS 5.1

[cove3]

I'm narrowing down my problem in getting FP extensions to work under IIS 5.1. thanks to help & insight from Stephan, Thomas, and others. I believe the answers to the 4 following questions will clear the mist, and show the sunlight, to myself & hopefully others

Assume I install IIS 5.1 with no server extensions & then download & install FP Extensions 2002. My Default Web directory is C://inetpub/wwwroot, but I can change it to any folder I create on my D drive. In order for any webs I create in FP 2002 using FP Extensions functions to work, I have to

1. In IIS, right click on My Default Web/All Tasks/Configure Server Extensions. This appears to add 6 folders and 25 files to my default root directory, I assume to allow the webs I create using DP extensions to function. This menu choice then goes away, I presume because I have "configured/enabled" FP Extensions. Is this correct

2. From here on out, if I create a discussion web using FP wizard, it should work because the wizard puts into the web some folders/files for FP Extensions to work/link to above folders. Is this correct

3. If I don't want to use the above wizard and want to create my own FP Extensions enabled web from scratch, the purpose of the right click on My Default Web/New/FP Extensions Web is to create a sub web containing the same FP Extension folders/files that the wizard in 2 above does. If I only use the wizard, I would never use this function. Is this correct

4. What I did by using the command prompt in Article 300543 owsadm.exe -o install -p 80 -us -sp publish was the same thing I could have done via #1, that is, what I was doing was configure/enable FP Extensions. Is this correct

I'm sorry for my difficulty with this; I think I got off on some blind alleys along the way & just sunk in deeper & deeper into confusion. Hopefully, I'm near the end. It's not easy being a webmaster, if only for a bulletin board for an IBM reunion function in April, after which my web will shut down. This is going to be a $5,000 board in my time, for which I hope to get perhaps 20-25 posts

Thanks & regards, Ro

 

[Jim Buyens]

-----Original Message-----

I'm narrowing down my problem in getting FP extensions to
work under IIS 5.1. thanks to help & insight from
Stephan, Thomas, and others. I believe the answers to
the 4 following questions will clear the mist, and show
the sunlight, to myself & hopefully others.

Assume I install IIS 5.1 with no server extensions &
then download & install FP Extensions 2002. My Default
Web directory is C://inetpub/wwwroot, but I can change
it to any folder I create on my D drive. In order for
any webs I create in FP 2002 using FP Extensions
functions to work, I have to:

1. In IIS, right click on My Default Web/All
Tasks/Configure Server Extensions. This appears to add
6 folders and 25 files to my default root directory, I
assume to allow the webs I create using DP extensions to
function. This menu choice then goes away, I presume
because I have "configured/enabled" FP Extensions. Is
this correct?
Exactly.

2. From here on out, if I create a discussion web using
FP wizard, it should work because the wizard puts into
the web some folders/files for FP Extensions to
work/link to above folders. Is this correct?

Yes, partially. Installing the FP Extensions also installs
an ISAPI filter named Shtml.dll that implements many of
the browse-time FPSE functions, such as discussion Webs.

3. If I don't want to use the above wizard and want to
create my own FP Extensions enabled web from scratch,
the purpose of the right click on My Default Web/New/FP
Extensions Web is to create a sub web containing the same
FP Extension folders/files that the wizard in 2 above
does. If I only use the wizard, I would never use this
function. Is this correct?

No. You can only install the server extensions to an
entire virtual server (or remove them from an entire
virtual server).

Subwebs are bodies of content that for one reason or
another needs to be treated differently. For example:

1. Different groups of people may be authorized to
update them.
2. They may contain different IIS applications.
3. They may contain bodies of content that are otherwise
convenient to treat as a group. For example,
FrontPage has Find In Web and Replace In Web
fucntion that limit their scope to the current subweb.

4. What I did by using the command prompt in Article
300543 owsadm.exe -o install -p 80 -us -sp publish was
the same thing I could have done via #1, that is, what I
was doing was configure/enable FP Extensions. Is this
correct?

Yes, exactly.

I'm sorry for my difficulty with this; I think I got off
on some blind alleys along the way & just sunk in deeper
& deeper into confusion. Hopefully, I'm near the end.
It's not easy being a webmaster, if only for a bulletin
board for an IBM reunion function in April, after which
my web will shut down. This is going to be a $5,000
board in my time, for which I hope to get perhaps 20-25
posts

Ah, but think of the knowledge you'll have gained!

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------