Skip to content

Releases: GriffinPlus/PreBuildWizard

Product Release 3.1.0

12 Apr 06:26
Compare
Choose a tag to compare

Features

  • Add --skipNugetConsistencyCheckPattern command line option

Product Release 3.0.2

06 Jan 06:41
Compare
Choose a tag to compare

Bugfixes

  • Fix warning emitted when C++ resource file has ASCII encoding.

Product Release 3.0.1

05 Jan 14:58
Compare
Choose a tag to compare

Bugfixes

  • Fix encoding being changed when patching CSPROJ files.

Product Release 3.0.0

11 Feb 08:52
Compare
Choose a tag to compare

This release updates from .NET Core 2.1 to .NET 5.0.

Product Release 2.0.1

06 May 08:49
Compare
Choose a tag to compare

Bugfixes

  • Fix crash in WiXProductFileProcessor

Product Release 2.0.0

06 May 06:52
Compare
Choose a tag to compare

Migration to using .NET Core

  • Providing two kinds of releases now: portable and standalone
    • Portable releases are not bound to a specific target. They require .NET Core 2.1 to be installed on the system to run the application. Due to the fact that no runtime components are shipped along with the application the release package is quite small.
    • Standalone releases are bound to a specific target and self-contained. They bring along .NET Core 3.1 runtime components needed to run the application. Therefore standalone releases are significant larger than portable releases.
  • Using Razorlight instead of the the Razor template engine (Razor is not compatible with .NET Core)

Changes

  • Replaced assembly version with major-minor-patch version when patching WiX installers (avoids updating installed rc-versions incorrectly).

Product Release of v1.4.1

16 Jul 11:10
Compare
Choose a tag to compare
Fix that exception messages are shown as output

 - the logging of an exception could result in empty lines for the output
 - this fixes the behavior by calling explicitly the ToString conversion

Product Release of v1.4.0

27 Jun 08:34
Compare
Choose a tag to compare
Add option 'BaseIntermediateOutputPath' to commandline parameters

 - the check for NuGet consistency can be configured with this parameter
 - with this option it expects the 'project.assets' under given path
 - NuGet consistency check is now an optional feature which is enabled when given the option
 - add more detailed usage information

Product Release of v1.3.2

21 Jan 07:15
Compare
Choose a tag to compare
Fixed AppVeyor integration.