|
| |
Updates
The current version of
Parastream PagePorter™ Professional is
1.1.1815. To
upgrade your REGISTERED VERSION, follow the instructions you received in your upgrade notice email. If
you did not receive an upgrade notice email, contact
Parastream customer service.
The current version of
Parastream PagePorter™ Demo is
1.1.1899. It expires
June 15,
2005. To upgrade from a previous DEMO VERSION, download and install the latest
DEMO VERSION from
here.
Change List
Click on a blue bullet dot to expand.
- 1.1.1815 – December 20, 2004
- Added another conversion option for converting controls - "Leave the
FrontPage file untouched." This is needed when re-converting shared border
controls.
- Converted pages that were marked as "Don’t publish" are now set to
"Build Action: None" instead of "Build Action: Content."
- The FpLinkBar.Target property now works with Graphics rendering.
- Fixed "Not implemented" exceptions when
opening Visual Studio Help projects.
- Navigation View no longer becomes the active tab every time PagePorter runs, unless it is set to Auto
Hide.
- Navigation View now defaults to all nodes expanded.
- Setup checks for Administrator rights
before proceeding.
- Setup can adjust the web folder file access
permissions.
- New setup option to display check for updates on PagePorter's first run.
- 1.1.1804 – December 9, 2004
- Changed version to 1.1.
- Minor documentation updates.
- The Make Home Page command is restricted to pages at the top level.
- The BasePage class for new projects has a default implementation of the
HandleBorderExceptions method override that throws an exception for controls
or code in the shared borders instead of catching them silently.
- Addressed problems with file access permissions (click to expand):
- If a file access permission exception is thrown in FpLinkBar, it will be
more descriptive than the previous "generic error in gdi+" exception.
- File access permissions are checked when the web application is started
to provide a "heads up" right away instead of waiting for an exception
within the application.
- Several changes to Navigation View (click to expand):
- Navigation View is not hidden for non-PagePorter projects. This
behavior is consistent with other tool windows.
- Navigation View state is properly maintained between design and run
mode.
- There is a known problem with Navigation View that causes it to
"flash" when Visual Studio .NET is started and when switching between
run and debug mode, only if Navigation View is set to "Auto Hide."
- The initial position for Navigation View is docked next to Solution
Explorer instead of the Toolbox, primarily to avoid the "Auto Hide
flash" problem.
- Editing the label in Navigation View causes the corresponding graphical
navigation button to be redrawn.
- The New PagePorter Web Site Wizard no longer saves a duplicate solution
file and directory [i.e. WebSite1 (2)].
- 1.0.1710 – September 6, 2004
- Fixed installer so it will allow PagePorter to install to Visual
Studio .NET or Visual Studio .NET 2003 even if Visual Studio 2005 (beta)
is installed.
- Fixed installer so items not selected from the list of multiple
Visual Studio installations will not have PagePorter installed to them.
- Added detection of the FrontPage Extensions web access method during
project creation and opening the project.
- If the project name gets changed after the New PagePorter Web Site
wizard starts, it no longer aborts with an error message.
- Changed the HTML comment tag used to mark shared borders from
<!-- fpsharedborder --> to <!--fpsharedborder-->.
- Theme CSS links are now correct when a new web form is created in a
folder that is not the project root.
- Changed the way PagePorter communicates the current file and
project paths to the web controls in the Visual Studio designer so it
handles multiple instances of Visual Studio.
- Fixed the FpLinkBar behavior that got confused by query
information after a question mark (?) in the URL of a page in Navigation
View.
- 1.0.1674 – August 1, 2004
|
