Soooooo, I tried to publish outside of the Inetpub\wwwroot folder, and I get error messages if I try to treat the new folder as a Web folder (http://virtual_web/whatever instead of c:\whatever). I tried using the Advanced section of PWS to create a whole new root folder (instead of just adding more Virtual Webs under the wwwroot folder), but it's not working.

Is there any way to do this, or does EVERY new "web" using PWS HAVE to be located under the initial wwwroot folder? Is this a problem JUST with Frontpage extensions or something? I ask because the folders DO show the little globe icon if I look at them w/ FrontPage's OPEN dialog box, but I still can't define them as http:// locations, and none of the ASP stuff works if they're outside the wwwroot folder.

ANY help would be appreciated, folks, and thanks for reading.

The Bot Collector

quote:

---

Originally posted by Botcollector:
(I can't use Frontpage to open the ASP pages, I'm sure you all know why)

---

quote:

---

Soooooo, I tried to publish outside of the Inetpub\wwwroot folder, and I get error messages if I try to treat the new folder as a Web folder (http://virtual_web/whatever instead of c:\whatever). I tried using the Advanced section of PWS to create a whole new root folder (instead of just adding more Virtual Webs under the wwwroot folder), but it's not working.

Is there any way to do this, or does EVERY new "web" using PWS HAVE to be located under the initial wwwroot folder? Is this a problem JUST with Frontpage extensions or something? I ask because the folders DO show the little globe icon if I look at them w/ FrontPage's OPEN dialog box, but I still can't define them as http:// locations, and none of the ASP stuff works if they're outside the wwwroot folder.

---

Well, first thing is PWS is not really web server, it's just a application that allows you to check a site in progress before publishing to a web server.

I'm not sure what you are doing - but when I did use, PWS I always created a site (folder) at Inetpub/WWWRoot/whatever - then published to http://127.0.0.1/whatever. Never had any problems.

------------------
Gil Harvey
The Host Factory
Resellers are our speciality
"Indecision may or may not be my problem"

Nope - why?

- END QUOTE -

Because FrontPage instantly leaps on the ASP code and destroys it, trying to rewrite it to some crazed Microsoft Wizard format. Any ASP coded page I've made or used outside of FP is always rewritten to no longer function by FP when a view attempt is made by clicking the "Normal" tab. I asked about turning all FP attempts to rewrite or verify ASP code off, but was told it can't be done.

When you publish to http://127.0.0.1/whatever, though, isn't that just putting the new web folder in C:/Inetpub/wwwroot/whatever? The actual file location of 127.0.0.1 is the wwwroot folder, isn't it? I need to publish to, say, C:\NOTwwwroot\Testing\whatever, and still have a browser be able to treat it as a web page, using http. Is the answer to this, then, that ANY webs published that can be viewed using http URL's (and functioning ASP pages) on the local drive instead of file:\\c:\whatever, etc. MUST be within the Inetpub\wwwroot folder? Is that the only location that PWS can work?

quote:

---

Originally posted by Botcollector:

Because FrontPage instantly leaps on the ASP code and destroys it, trying to rewrite it to some crazed Microsoft Wizard format. Any ASP coded page I've made or used outside of FP is always rewritten to no longer function by FP when a view attempt is made by clicking the "Normal" tab. I asked about turning all FP attempts to rewrite or verify ASP code off, but was told it can't be done.

---

quote:

---

When you publish to http://127.0.0.1/whatever, though, isn't that just putting the new web folder in C:/Inetpub/wwwroot/whatever? The actual file location of 127.0.0.1 is the wwwroot folder, isn't it? I need to publish to, say, C:\NOTwwwroot\Testing\whatever, and still have a browser be able to treat it as a web page, using http. Is the answer to this, then, that ANY webs published that can be viewed using http URL's (and functioning ASP pages) on the local drive instead of file:\\c:\whatever, etc. MUST be within the Inetpub\wwwroot folder? Is that the only location that PWS can work?

---

Well, the only way a browser can treat a HTML or ASP document as a web "page" is if it's called with a HTTP protocol. So, yes PWS will only work for documents that can be accessed by HTTP://whatever

But, why do you say "I need to publish to, say, C:\NOTwwwroot\Testing\whatever"???

------------------
Gil Harvey
The Host Factory
Resellers are our speciality
"Indecision may or may not be my problem"

quote:

---

Originally posted by Botcollector:
I need the new Web folder to be located outside of the c:\Inetpub\wwwroot\ folder.

---

quote:

---

I need to use Frontpage to publish a Web on my local hard drive that resides anywhere but the Inetpub\wwwroot folder. The new web must be accessible as an http-called page, and the stuff PWS does must still work (ASP pages, for instance, which do not seem to work outside of the wwwroot folder). This is what I mean when I say I need to publish to c:\\NOTwwwroot. When you publish anywhere using http://127.0.0.1/, it's just making the new web as a subweb of the wwwroot folder. Is there a way to publish outside the wwwroot folder on a local harddrive and still access the pages w/ http protocol?

---

I'm not even sure what "subweb" is supposed to mean, that's a MS term for a directory under the root of a web site.

I've published three copies of the same web (using a different name, of course) as virtuals many times using PWS.

I feel there is a way to do what you need, but can't figure out why you "need" to publish outside WWWRoot?

------------------
Gil Harvey
The Host Factory
Resellers are our speciality
"Indecision may or may not be my problem"

"This root web is already the DNS resource (or something similar) for 'my original website name'. This may cause problems with the functionality of the root web and websites. Do you wish to proceed?"

Naturally, I do not wish to proceed. I would rather establish a new web outside the wwwroot folder, which will still allow PWS to perform as a "web server" for the new web.

quote:

---

Originally posted by Botcollector:
The new web needs to be outside of wwwroot because when I use UltraDev to try and edit the ASP pages (because FrontPage tries to automatically tear them up), it shows an error message stating:

"This root web is already the DNS resource (or something similar) for 'my original website name'. This may cause problems with the functionality of the root web and websites. Do you wish to proceed?"

Naturally, I do not wish to proceed. I would rather establish a new web outside the wwwroot folder, which will still allow PWS to perform as a "web server" for the new web.

---

Hmm, I've never seen the error you are getting - but then I don't use ASP or MS databases...

All, I can say is I don't see any way to have a web site not accessed by a web browser that will allow ASP pages to function.

Sorry, I couldn't help...

------------------
Gil Harvey
The Host Factory
Resellers are our speciality
"Indecision may or may not be my problem"