Right. You can have a web -- typically default web in d:\inetpub\wwwroot
and have (or have not) extended. There should be no issues with also
having an extended web in d:\inetpub\somethingelse either. Just don't
expect it to work if you it in d:\inetpub\wwwroot\somethingelse.
FrontPage2000 and higher will have kittens with that. And don't extend a
d:\inetpub itself. More kittens if you do.

The build of the .NET run time from 2/15/2002 forward seems to be
nonplus to this issue. I suspect you're fine using the Everett (1.1)
build as you've described. I've run that since for weeks without issue.

And I swear that someplace in the core logic of IIS that if it detects
that FPSEs have installed, it enumerates the various admin groups puts
us on it's "people whose's heads I need to mess with" list.

kt

-----Original Message-----
From: Okie Tex [mailto:okie_tex@;hotmail.com] 
Sent: Thursday, November 07, 2002 10:28 PM
To: IIS50 Discussions
Subject: RE: .net and FrontPage


Thanks Kent for the information

let me clarify one thing ...

>I don't recall having heard of it requiring diverse volumes however.

well, what I mean is that I can have webs that will work with FrontPage 
Extensions either at c:\WHATEVERDIR\ or another volume/drive d:\ or e:\ 
etc... and it will work.

I just never made it work having any web server with FrontPage EXTs
under 
the "default" c:\inetpub\ directory...  that was where I was testing and
it 
just wouldn't work.  And, maybe they are forcing you now to not do
that??

Well -- maybe I'm nuts on this... maybe I've gone or going crazy!
Yesterday 
I tested this on 2 other machines and it did what I said above and in
the 
original post.  Now, on 2 different machines (equipped close to the same
... 
different .NET install though), it isn't doing what I'm saying ...

anyway -- sorry for posting ... but now I'm confused and will have to
figure 
out where my differences are and if I was *seeing* things!!!!

thanks for helping out! -jason




>From: "Tegels, Kent" <[EMAIL PROTECTED]>
>
>It seems to be that's as well known as any of FPSE quirks. The basic 
>reason
>is seems to have stemed from problems in IIS4 with people putting
isolated 
>process webs inside of a root web that was left in-process. I seem to 
>recall that this would really hose things up. There's a different chunk
of 
>bits dropped in the various _VTI_* folders that frontpage uses
depending on 
>if its a root web and such. I don't recall having heard of it requiring

>diverse volumes however. We've got a number of servers where the roots
are 
>all under e:\inetpub. The trick seems to be not extended that
particular 
>root folder.
>
>Having scripts that generate the Vroot and apply the extensions 
>generally
>makes the process less error prone.
>
>HTH,
>kt
>
>       -----Original Message-----
>       From: Okie Tex [mailto:okie_tex@;hotmail.com]
>       Sent: Thu 11/7/2002 11:59 AM
>       To: IIS50 Discussions
>       Cc:
>       Subject: Re: .net and FrontPage
>
>
>
>       To answer 1 of my questions ... here you go -- see below:
>
>       >All that leads to my next question regarding FrontPage.  On the

>server
>that
>       >I was installing .NET, it has FrontPage Extensions installed.
Now, my
>       >problem arises when I create a virtual web server and try to
create FP 
>Exts
>       >... there is no option for me to do this?
>       >
>       >Has anyone seen this before?  Is it related to me messing
around with 
>.NET?
>       >(on the latter ... I've installed .NET a few months back and
didn't have
>       >this problem).
>
>       This is very interesting -- I had create a folder in my
\inetpub\ folder
>       called \inetpub\webtest\  -- well, that wasn't working (ie, with

>getting
>the
>       front page extensions admin to show up.
>
>       So, I created  another web and made my source on another volume
- sure
>       enough, the FrontPage Admin showed up and I was able to install
the
>       extensions.
>
>       So - maybe this is well known (but I didn't or didn't remember
it), you
>       can't put anything in \inetpub\ and have a virtual web server
work 
>with
>that
>       web server.  (this is on an W2K/SP3/IIS5/FP v4 (then upgraded to
v5) and
>       .NET installed.
>
>       Anyway, it was driving me nuts but now I got it.  Anyone know
why
>MS/IIS/FP
>       doesn't like any other webs in the \inetpub\ folder.  I don't
like putting
>       my client webs there anyway ... but was just testing and found
this out.


_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE* 
http://join.msn.com/?page=features/junkmail


---
You are currently subscribed to iis50 as: [EMAIL PROTECTED]
To unsubscribe send a blank email to
%%email.unsub%%

---------
Administrated by 15 Seconds : http://www.15Seconds.com
List Archives/Search : http://local.15Seconds.com/search
Subscription Information : http://www.15seconds.com/listserv.htm
Advertising Information: http://www.internet.com/mediakit/



---
You are currently subscribed to iis50 as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]

---------
Administrated by 15 Seconds : http://www.15Seconds.com
List Archives/Search : http://local.15Seconds.com/search
Subscription Information : http://www.15seconds.com/listserv.htm
Advertising Information: http://www.internet.com/mediakit/


Reply via email to