Personal Web Server


D

Dennis D.

Hello:

Apps: Windows XP Pro, FP 2003, IIS 5.1, SQL Server Express Edition 2005

PWS no longer being used, are there any options for setting up a personal
web server on XP Pro so that FrontPage components can be tested prior to
deployment? Downloaded and Installed SSEE 2005 and FPSE 2002 on IIS 5.1, but
FP still pops up the import type FPSE, WebDav, FTP ... dialog, and errors
out when I try to open http://localhost/d3. SQL SEE 2005 is running.

Thanks,

Dennis,
http://www.dennisys.com/
.... Site down for the holidays
 
Ad

Advertisements

T

Tom [Pepper] Willett

WinXP Pro uses IIS 5.1. You install it from Add/Remove programs or the CD.
You don't use a PWS.
--
===
Tom [Pepper] Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/

About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
===
| Hello:
|
| Apps: Windows XP Pro, FP 2003, IIS 5.1, SQL Server Express Edition 2005
|
| PWS no longer being used, are there any options for setting up a personal
| web server on XP Pro so that FrontPage components can be tested prior to
| deployment? Downloaded and Installed SSEE 2005 and FPSE 2002 on IIS 5.1,
but
| FP still pops up the import type FPSE, WebDav, FTP ... dialog, and errors
| out when I try to open http://localhost/d3. SQL SEE 2005 is running.
|
| Thanks,
|
| Dennis,
| http://www.dennisys.com/
| ... Site down for the holidays
|
|
 
A

Andrew Murray

IIS 5.1 is your web server (running locally on XP Pro) which you've listed
below as already installed.

Publish from FP to C:\Inetpub\wwwroot\yoursite on your hard drive; then view
the site in your browser with http://localhost/yoursite
 
R

Ronx

Publish from FP to C:\Inetpub\wwwroot\yoursite
Do that and your web site is as good as dead.

A file destination will produce a disc based web, which is useless for
testing server side components against a web server.
Publish to http://localhost/websitename websitename being a subweb
that will contain your web site. Publishing to a subweb allows you to
create other server based webs alongside each other.
 
A

Andrew Murray

I have it working like that; I publish from FP to "c:\inetpub\wwwroot" and
can view it with http://localhost. (that's what the
documenation/instructions say to do, to publish the site).

I think I actually meant in my reply to publish to "c:\inetpub\wwwroot"
(drop the "yoursite" from the end) and it works - for me - when viewed with
http://localhost

Anyway point was the OP was asking about an alternative to PWS which IIS in
XP Pro provides.
 
R

Ronx

Publishing to a file location will always produce a disc-based web.
Forms (for example) produced on a disc based web will never work,
until they are _published_ to a server. It is pointless having a
server if all you are "testing" is a web designed for a file system
environment.
Whoever gave you those instructions to publish to a file system
location have led you astray. (Actually it will work, provided you do
not use any FrontPage components that require the Server extensions,
like Hit Counter, Forms, custom link bars etc. etc.)
The OP was talking about testing his web site locally. <quote> so
that FrontPage components can be tested prior to deployment?</quote>
This requires a server with a server based web, not a server with a
disc based web.
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top