Skip to content

White Tie 1.3.16

Latest
Compare
Choose a tag to compare
@RxDave RxDave released this 26 May 02:07
· 4 commits to master since this release

White Tie is available as a NuGet package.

New In This Release

  • Fixed a bug that caused flavor projects to be built multiple times.
  • Fixed a bug that caused the NuGet command to produce a package from the project file rather than the generated .nuspec file, in some situations.
  • (From v1.3.15): Added support for the new portable reference type introduced in VS 2015, ImplicitlyExpandDesignTimeFacades. This fixes an issue when targeting portable libraries in VS 2015, which caused all system references to be added to the NuGet package.
  • (From v1.3.15): Fixed a bug that would cause an invalid PackageId and Version to be generated for duplicate recursive flavor dependencies.

New In Recent Releases

  • Support for Visual Studio 2015 without requiring NuGet Package Restore to be enabled on the solution.
  • Future-proofed for new VS releases so that the lib folder name is inferred from the target framework rather than requiring White Tie to be updated with explicit mappings; e.g., a hypothetical v4.6.2 will become net462.
  • Fixed Sandcastle colorizer reference path (thanks to contribution from drmannion)
  • Fixed a bug that caused a fatal build error for certain kinds of projects; e.g., a WPF application project.
  • Fixed a bug that caused NuGet to fail with duplicate dependency errors in certain scenarios.
  • Builds documentation when Sandcastle is installed.
    • The compiled help file is also added to the NuGet package, if one is generated.
  • Can now optionally build a "development dependency" package.
  • Supports additional target Framework "flavors" in the NuGet package via special project references.
    • Includes deeply referenced assemblies, NuGet dependencies, Code Contract assemblies, serialization assemblies, symbols and XML documentation files.

About Target Framework Flavors

This feature allows non-referenced projects to be included as "flavors" of the current project's NuGet package. Each flavor is placed in its specific target framework folder under the lib folder in the NuGet package.

To include a target framework flavor, you must edit your project file and add the following XML element:

<NuGetFlavor Include="..\other\other.csproj" />

See @(NuGetFlavor) for details.