|
| |
|
|
|
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
Important: RegistrationIf 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
Installation InstructionsInstalling and Uninstalling PagePorterTo install PagePorter, follow these steps:
To uninstall PagePorter, follow these steps:
Installing Class Library HelpIn the retail versions of PagePorter, you have three options regarding the documentation for the PagePorter Class Library:
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 StudioIf 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 IssuesYou 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 IssuesAccess Permissions and “Access Denied” ErrorsBy 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:
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 DisplayingThe shared borders do not display in design mode. You must preview the page in the browser, or run the application. Web Access MethodPagePorter 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 FoldersIf 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 ErrorsWhen 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:
© 2004 Parastream Technologies, Inc. All rights
reserved. |
|
© 2002-2006 Parastream Technologies, Inc. All Rights Reserved. Last modified: March 02, 2009. |