changes made in this release:

Sandcastle
- BREAKING CHANGE: Added a new ResourceItemFileLocation property to the syntax generator factory interface. This is implemented to return the path to the resource item file associated with the syntax generator containing its localized text for titles, messages, metadata, etc. This allows creation of self-contained syntax generators that require no modifications to the presenation styles with which they will be used.
- Fixed a bug in SyntaxComponent so that it doesn't crash if a syntax generator does not specify any alternate IDs.
- Added code to MRefBuilder to properly match types and methods with generic parameters under specific conditions. Thanks to Jared Moore for reporting the issue with a test case.
- Added code to MRefBuilder to write method parameter attribute elements to the reflection information file.
- Added code to MRefBuilder to write out the value of literal (constant) fields to the reflection information file.

Sandcastle Help File Builder
- Fixed the DBCS Fix plug-in so that it copies the Help 1 content to the output folder for inclusion in the localized copy of the content.
- Fixed the XPath Reflection File Filter plug-in so that it runs before transforming the reflection file content and generating the BuildAssembler manifest file.
- Fixed the Lighweight TOC plug-in so that it adds some script to the default topic to expand the root node when the first node has children. This prevents it from looking like only one namespace was documented because the root node is collapsed.
- Applied a fix from Kalyan00 to the Sandcastle HTML Extract tool so that it correctly saves files in the localized and original locations with the proper encodings.
- Added code to the C# documentation completion provider to disable it if the Roslyn package is installed. The Roslyn package uses an incompatible implementation of IntelliSense and the extended completion provider cannot be used with it for now.
- As suggested by Kaylan00, the DBCS Fix plug-in has been changed so that the path to the SBAppLocale tool is optional. If not specified, the plug-in will issue a warning but will run. In such cases, only the localization fixes applied by the Sandcastle HTML Extract tool will be in effect.
- Merged a few style changes to the VS2013 website stylesheet from Sam Harwell related to the resize/drag divider.

Presentation Styles
- BREAKING CHANGE: Moved the syntax generator resource items to the syntax generator BuildAssembler project. This allows the syntax generators to be more self-contained and allows them to be created without requiring changes to the presentation styles.
- BREAKING CHANGE: Updated the Open XML, VS2010, and VS2013 presentation styles so that they are no longer dependent on the syntax generator items and IDs.
- Fixed the copyright replacement tags in the SHFB content files so that they use the HTML encoded text.
- Fixed an invalid end element in the German and Russian language versions of the enumerationOverviewXamlSyntax element.
- Fixed the VS2010 and VS2013 presentation styles so that code blocks with line numbers and/or collapsible sections are copied to the clipboard without those elements.
- Added support for including conceptual links in overloads elements.

https://shfb.svn.codeplex.com/svn@106513
changes made in this release:

General
- Removed all FxCop project files and added code analysis rule sets for all projects except the VSPackage. All projects except the VSPackage project will now be maintained in VS2013. The VSPackage project is still being maintained with VS2010 as I need to build it for the lowest version supported.
- Fixed up some issues found while using the new code analysis rule set.

Sandcastle Help File Builder
- BREAKING CHANGE: Moved the colorizer files from the Sandcastle Builder GUI project to the Presentation Styles project where they are a better fit. This changes the location of the colorizer files and places them under the PresentationStyles\ folder. If you have added the Code Block Component to your project, you will need to remove it and re-add it or update the configuration to add the "PresentationStyles\" folder ahead of the "Colorizer\" folder in the configuration file location options.
- Moved the SandcastleBuilderGUI\Templates folder content to the SandcastleBuilderUtils project since it is really related to the build engine more than the GUI.
- Moved the LaunchMSHelpViewerDlg form from the Sandcastle Builder GUI project to the Sandcastle Builder Utils project.

Presentation Styles
- BREAKING CHANGE: Moved the colorizer files from the Sandcastle Builder GUI project to the Presentation Styles project where they are a better fit. This changes the location of the colorizer files and places them under the PresentationStyles\ folder. All BuildAssembler configuration files in custom presentation styles that utilize the Code Block component will need to be updated to add the "PresentationStyles\" folder ahead of the "Colorizer\" folder in the configuration file location options.

https://shfb.svn.codeplex.com/svn@106516
changes made in this release:

General
- A SandcastlePackage_VS2013.sln and related project files have been created so that the VSPackage can be build with VS2013 if necessary for testing.
- Added a build step to generate a NuGet package (EWSoftware.SHFB) to allow for build server deployments and local project copies of the tools that can be checked into source control.

Documenation
- Added information to the XML Comments Guide about using NamespaceGroupDoc classes.
- Added help topics to the SHFB help project for the new IntelliSense Only and Member ID Fix-Ups plug-ins.
- Update the release notes in the Sandcastle Tools and SHFB help projects.

Sandcastle
- Added code to ResolveReferenceLinksComponent and CopyFromIndexCommand to check for and use broken EII member IDs if the correct one is not found. This works around a bug in the base framework XML comments file member IDs and the MSDN content service IDs for certain inherited EII members. NOTE: You will need to delete the content ID cache in order for this change to have any effect.
- Added a new namer to MRefBuilder for Windows Store and Windows Phone frameworks that renames certain core types that the compiler changes when building assemblies. This ensures that the reflection data matches the XML comments data.
- Fixed MRefBuilder so that it filters out duplicate member IDs from derived interfaces that re-implement base members using the "new" keyword.

Sandcastle Help File Builder
- Fixed the Version Builder plug-in so that it correctly generates the version IDs used in the configuration file and the label resource items. It is now possible to have "prior" projects that use different framework labels with a version number that matches the "current" project.
- Fixed the Additional Reference Links and Version Builder plug-ins so that they correctly apply the Configuration and Platform properties to the sub-projects to ensure they are evaluated properly in project properties when the sub-projects are loaded.
- Fixed the VSPackage IntelliSense provider by adding "langword" as a prefix to the language keyword entries to prevent an odd crash in VS 2013.
- Fixed the Lightweight TOC plug-in so that it transforms the help title property value to ensure substitution tags in the value are replaced.
- Set the maximum degree of parallelism in the Sandcastle HTML Extract tool to 20 threads per processor. This is configurable but is not currently exposed. It can be adjusted by adding a MaxDegreeOfParallelism property to the HTML extract project template and passing it to the task if needed.
- Added support for NamespaceGroupDoc classes in XML comments files to add documentation to namespace group topics.
- Added the Member Id Fix-Up Plug-In to allow fixing up member IDs in XML comments files that do not match the reflection data due to quirks in the various compilers. This can be used in place of or in conjunction with the C++ Fix-Up project property.
- Added the IntelliSense Only plug-in that can be used to suppress the help file build steps and produce only the IntelliSense XML comments files when used in conjunction with the IntelliSense build component. This is useful for supporting projects that need IntelliSense XML comments files but do not contribute content to the help file directly (i.e. those in the Version Builder plug-in configuration).
- Added support for installing the VSPackage in Visual Studio 2015 Preview.

Presentation Styles
- Fixed the code contracts templates so that the inherited property member IDs in reference links are rendered correctly.
- Removed an extraneous comma in the VS2013 branding-Website.js file which was causing problems in Internet Explorer (reported by baerbradford).

https://shfb.svn.codeplex.com/svn@106927