Version 1.9.3.4 (Beta 2) |
Version 1.9.3.4 was released on January 30th, 2012.
The primary purpose of this release is to move the Visual Studio Integration Package into a beta stage so that more people can start using it and to test and get feedback on the new file editors and the new topic previewer window. The build engine and the package in general are quite stable and are suitable for general use. As before, if there are issues you can drop back to the last stable release as there have been no changes that would affect the project file format. However, some support for newer features such as Portable Framework and Silverlight 5 support are not available in the prior stable release.
With this release, the Visual Studio package now matches the standalone GUI with regard to features and functionality. Projects can now be managed completely from within Visual Studio without having to open a copy of the project in the standalone GUI. For more information on the new features available in the beta release, see the following help topics:
Updated the build log viewer tool window in the standalone GUI and VSPackage to use the new shared build log viewer WPF user control. The new control uses a default setting of plain text which loads much faster. It also provides options to highlight warnings and errors and to filter the log to only show warnings and errors.
Removed highlighting of script names from the build log XSL transformation as it wasn't really useful anymore since they all refer to MSBuild.exe now. Also made the warning and error regular expressions case sensitive which improves the loading speed a bit when filtering. The warning and error text is typically in a fixed style case-wise so this shouldn't be an issue.
Removed the Filter Log setting from the standalone GUI settings and the VSPackage tool window since it is no longer used.
Added the New Project from Other Format project template to the VSPackage to allow the creation of new projects from other file formats from within Visual Studio.
Fixed a bug in the base project converter class caused by the way MSBuild 4.0 adds new file items to projects. The file paths are typically fully qualified rather than relative on newly added items.
Added a new shared topic previewer WPF user control. This new version is a complete rewrite of the topic previewer from past versions. Instead of doing a partial build on the conceptual content, it now converts topics to flow documents on the fly. This significantly reduces the time needed to preview a topic and lets you view any topic in the project via links in the topic or using the new table of contents tree view that appears in the browser. The control also takes into account unsaved changes in all token, content layout, and topic files when presenting them so that current content is displayed regardless of whether or not you have saved changes to all of the affected files.
Updated the topic previewer window in the standalone GUI to use the new shared topic previewer control.
Added the topic previewer window feature to the VSPackage. You will find it on the View | Other Windows menu and in the Other Windows tool bar button dropdown.
Updated the GenerateInheritedDocs tool as follows:
To provide default comments for the compiler-generated WPF attached property and attached event class members, it retrieves the comments from the related backing field if comments do not exist for the related compiler-generated members already. This provides default comments for them rather than a "missing comments" warning.
If comments are found for the attached property or event field and they contain an AttachedPropertyComments element (for attached properties) or an AttachedEventComments element (for attached events), it will use the nested XML comments from those elements instead for the related compiler-generated member. This allows adding different comments for the field and the auto-generated property/event members but keeps them all on the related field to make managing the comments much easier.
It now skips inherited documentation for members that do not appear in the reflection information data file. This suppresses unnecessary GID0003 warnings for the excluded members because it cannot find the comments to inherit.