Wrox Programmer Forums
|
BOOK: ASP.NET Website Programming Problem-Design-Solution
This is the forum to discuss the Wrox book ASP.NET Website Programming: Problem - Design - Solution, Visual Basic .NET Edition by Marco Bellinaso, Kevin Hoffman; ISBN: 9780764543869
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: ASP.NET Website Programming Problem-Design-Solution section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old April 9th, 2004, 11:11 AM
Registered User
 
Join Date: Apr 2004
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default Frontpage extension Help plz

Hi all,

Hopefully this is the correct forum to post this at. If not please direct me to the correct forum.

I am learning with Beginning C# (Kari Watson ISBN 1.861004.98.2) I am trying to do the example in case study #1 Web Site Poll. I am running Win XP Pro, Visual Studio.NET 1.0 Enterprise, Framework 1.1, MS Office is not installed, I do have all the Win Components for IIS installed.

I am having problems with the install of the frontpage extension and hopefully someone can help because this is causing errors with the execution of the sample. Under Admin tools/Computer Management/Services and Applications/Internet Information Services/Web Sites/Default Web Site, I have right clicked selected new Tasks then tried to click on "Open with FrontPage extension". Here the message reads "You need to install the FrontPage client software to open a web with FrontPage" appears.

Now I have read the previous post "Access to the path "C:\Inetpub\wwwroot\wrox\ThePhi" and all the related links. The syntax for reading the the xml file works fine enough "FileStream fs = new FileStream(fileName, FileMode.Open, FileAccess.Read);", but I am receiving errors while click on "vote" button to cast a vote. All book codes seem correct. Also even though this syntax works, is this actually the correct/standard code "FileAccess.Read" for opening xml's or just a quick fix?

Sorry about the long question. Thank you all in advance for any and all help given.

MikeY

 
Old April 9th, 2004, 03:54 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 917
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Control panel, Add/Remove programs, click on Add/Remove Windows components, click on IIS, click on Details, check the box by Front Page extensions.

2 notes for you:
1) don't mess with the new folders you see that begin with underlines - these are used by the FP extensions
2) don't do this on a production computer, unless you go to the trouble of setting up Windows auth security for the FP extensions. Without added security, anyone can open projects on your computer.
 
Old April 9th, 2004, 04:18 PM
Registered User
 
Join Date: Apr 2004
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Txs Englere. But I have already have the Window Components installed for IIS/Frontpage and still having the problems, hmmmmm.

 
Old April 12th, 2004, 12:48 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 917
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Maybe you deleted the special folders used by FP?

Or maybe you have an NTFS permissions issue?

Or maybe the virtual dir isn't set as an application in IIS?

If you can't figure it out, try removing the FP extensions and re-installing them.





Similar Threads
Thread Thread Starter Forum Replies Last Post
FrontPage issue Mogg-Way HTML Code Clinic 1 February 21st, 2008 08:17 AM
Frontpage 2002? patwadd Classic ASP Basics 1 February 17th, 2005 07:12 PM
How to use html extend Frontpage Server Extension? keenx C# 0 May 31st, 2004 02:09 AM
Searching with access and frontpage kendals Classic ASP Basics 0 October 14th, 2003 04:00 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.