Skip Navigation Links
 Home 
 IMSAI 
 WANTED! 
 Library 
 Testimonials 
 Press 
Parastream Technologies Logo Search | Cart


Sign In
Skip Navigation Links
 Software Expand Software
 Hardware Expand Hardware
 Consulting Expand Consulting
 Support Expand Support
 Free Stuff 

Parastream PagePorter Read Me

December 2, 2004

Welcome to the Parastream PagePorter™ Read Me. For general product usage and troubleshooting information, consult the on-line help by selecting PagePorter Help from the PagePorter menu, or go to http://pdc.parastream.com/library/default.asp?url=/library/dotnet/pageporter/doc/index.htm.

Contents

Registration
System Requirements
Installation Instructions
Installing and Uninstalling PagePorter
Installing Class Library Help
Installing with Multiple Versions of Visual Studio
Installation Issues
Troubleshooting Issues
Access Permissions and “Access Denied” Errors
Shared Borders Not Displaying
Web Access Method
Use IIS to Delete Web Files and Projects
“Parser Error Message: Access is denied” and “LOG: Publisher policy file is not found” Runtime Errors

Important: Registration

If you purchased PagePorter directly from Parastream web site’s online store, your copy of PagePorter was registered automatically at the time of purchase. If you purchased PagePorter from a reseller, you may either fill in the registration card or you may go to http://www.parastream.com/register and register your copy of PagePorter online. You must register to receive technical support, and to receive notices of upgrades and other offers from Parastream.

System Requirements

  • Microsoft Visual Studio .NET or Visual Studio .NET 2003. Visual Studio 2005 is not currently supported, but will be shortly after its release.
  • Microsoft Internet Information Services and FrontPage Server Extensions.
  • Microsoft Windows 2000 SP3+, Windows XP, or Windows Server 2003.
  • Microsoft FrontPage 98 or later if web site co-management is desired.

Installation Instructions

Installing and Uninstalling PagePorter

To install PagePorter, follow these steps:

  1. Make sure you have at least 5MB of available disk space.
  2. Make sure you have Visual Studio .NET or Visual Studio .NET 2003 on your system before installing since PagePorter requires this software.
  3. Shut down any running instances of Visual Studio .NET.
  4. Turn off all anti-virus software before beginning the installation.
  5. Install PagePorter.

To uninstall PagePorter, follow these steps:

  1. Shut down any running instances of Visual Studio .NET.
  2. From the Start menu select Settings, Control Panel, Add/Remove Programs
  3. Select PagePorter and press the Remove button

Installing Class Library Help

In the retail versions of PagePorter, you have three options regarding the documentation for the PagePorter Class Library:

  1. Integrate the Class Library help into Visual Studio. This is the recommended option, which will enable context-help for the code editors.
  2. Install the Class Library help as a separate HTML help file. Choose Class Library Help from the PagePorter menu to access.
  3. Do not install the Class Library help. You may access it on-line at http://pdc.parastream.com/library/default.asp?url=/library/dotnet/pageporter/classlib/index.htm.

In the demo version of PagePorter, there is no Class Library help included. You may access it on-line at http://pdc.parastream.com/library/default.asp?url=/library/dotnet/pageporter/classlib/index.htm.

Installing with Multiple Versions of Visual Studio

If you have more than one version of Visual Studio .NET installed on your computer, Setup will let you choose which versions of Visual Studio will have PagePorter installed. Note, however, that if you choose to integrate the Class Library help into Visual Studio .NET, it will be integrated into all versions regardless of this choice.

Installation Issues

You must have administrative privileges to install PagePorter.

After installation, you must verify that you have the proper rights to read and write files in the web site at runtime. Although you will be able to create a web site without doing this, many of PagePorter’s features such as graphical navigation buttons will fail if you do not. The best way to do this is to follow the instructions in the Access Permissions and “Access Denied” Errors section. For more information, see the “Web Application Security in IIS and ASP.NET” section on the Microsoft web page Web Application Security At Design Time In Visual Studio.

Repairing the installation - If the PagePorter installation has become damaged, you can repair your installation. From the Start menu select Settings, Control Panel, Add/Remove Programs. From the dialog that comes up, select PagePorter and then press the Change button to repair your installation.

Troubleshooting Issues

Access Permissions and “Access Denied” Errors

By default, Visual Studio .NET does not set up proper file access permissions for PagePorter web sites to run successfully in all cases. Here’s the quick way to check and correct the problem:

  1. Using Windows Explorer, navigate to the Web Root Folder (usually C:\Inetpub\wwwroot).
  2. Right-click on the folder and choose Properties.
  3. Select the Security tab. If you do not see the Security tab with Windows XP, you must disable "Simple File Sharing." From the Windows Explorer menu choose Tools, Folder Options, View tab, and uncheck the Use simple file sharing (Recommended) option. This will enable the Security tab on file and folder property dialogs.
  4. Look in the Group or user names list for aspnet_wp account (machine_name\ASPNET) where machine_name is the name of your computer. If it is not present, click the Add... button and type ASPNET in the box and click the OK button.
  5. Select the aspnet_wp account (machine_name\ASPNET) user. Make sure the Allow check boxes are checked for the Modify and Write permissions. Click the OK button.

PagePorter needs to be able to create, modify, and delete files within the application folder for some features to work, such as the graphical buttons in the Link Bar control. For security reasons, Microsoft created the ASPNET user to run ASP.NET processes with minimal access rights. When you run the web project or preview a page in the browser, the ASP.NET worker process runs the ASP.NET code with the ASPNET user’s access rights. By default, ASPNET can only read files and cannot write them. Even though your user login has permissions to write files in the application folder, the ASP.NET user does not by default. The procedure described above will grant read and write access to all web folders to the ASPNET user. Alternatively, you may apply the access permissions only to those web folders that need it for added security.

For more information, see the “Web Application Security in IIS and ASP.NET” section on the Microsoft web page Web Application Security At Design Time In Visual Studio.

Shared Borders Not Displaying

The shared borders do not display in design mode. You must preview the page in the browser, or run the application.

Web Access Method

PagePorter web site projects require the file share web access method to avoid conflicts that occur with the FrontPage Extensions method. With Visual Studio .NET, you may choose either FrontPage Extensions or file share for the method used to access the local files in the web project. The default method is file share, but may be changed by choosing Options... from the Tools menu, then choosing Projects, Web Settings, and setting the Preferred access method.

Use IIS to Delete Web Files and Folders

If you need to delete a web file or project, don’t use Windows Explorer on the inetpub/wwwroot/<project> folder. Use the Internet Information Services Management Console instead. From the Start menu select Settings ► Control Panel ► Administrative Tools. From there, select the Internet Information Services icon. Under Web Sites, Default Web Site, navigate to the project file or folder you want to delete.

“Parser Error Message: Access is denied” and “LOG: Publisher policy file is not found” Runtime Errors

When developing a PagePorter project locally, if you get an “Parser Error Message: Access is denied” and a “LOG: Publisher policy file is not found” message when attempting to run the application. The Windows Indexing Service is the culprit. You must turn Indexing Service off by using one of these methods:

  • Windows 2000 : Select Start ► Search ► For Files or Folders... Under Search Options, click the Indexing Service link if it is not currently disabled and choose No, do not enable Indexing Service.
  • Windows XP : Select Start ► Search ► For Files or Folders... Click Change Preferences. Click With Indexing Service (for faster local searches) and choose No, do not enable Indexing Service.

© 2004 Parastream Technologies, Inc. All rights reserved.
PagePorter is a trademarks of Parastream Technologies, Inc. Parastream is a trademark of Parastream Technologies, Inc. Microsoft, FrontPage, Visual Studio, Windows, the Windows logo, Windows 98, Windows NT, Windows 2000, and Windows XP are either registered trademarks or trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.



Contact Us  |  Feedback  |  Ordering  |  Privacy  |  Legal  |  Partners  |  About

© 2024 Parastream Technologies, Inc. All Rights Reserved.