Changelog

All notable changes to ReSharper.ExportAnnotations will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased changes

New features

Changes to existing features

Bugs fixed in this release

Known problems introduced by this release

1.4.0 (2022-04-01)

Changes to existing features

POTENTIALLY BREAKING CHANGE: Support has been dropped for .NET Framework versions prior to 4.7.2, all versions of .NET Core (.NET 5 and newer is of course supported), and MSBuild versions prior to 16.8 (Visual Studio 2019 v16.8, .NET SDK v5.0).

1.3.2 (2021-09-13)

Changes to existing features

Now using Mono.Cecil v0.11.4.

Bugs fixed in this release

JetBrains.Annotations.dll, or whatever is the specified annotations package, is now retained in the output folder if StripJetBrainsAnnotations is false.

1.3.1 (2020-10-10)

Bugs fixed in this release

#23 - Builds fail on non-Windows systems.

1.3.0 (2020-10-06)

New features

ReSharper.ExportAnnoTations.Core now supports .NET Framework 4.6 in addition to .NET Standard 2.0.

Bugs fixed in this release

#20 - Building a project with dotnet build using .NET Core SDK v3.1 or .NET SDK 5-rc1 does not require.NET Core 2.1 to be installed any longer.

1.2.1 (2020-10-04)

Changes to existing features

ReSharper.ExportAnnotations.Task now skips most operations, including sanity checks, during design-time builds.

Bugs fixed in this release

ReSharper.ExportAnnotations.Core's symbol package now contains correct links to source code.
Projects referencing ReSharper.ExportAnnotations.Task but not referencing JetBrains.Annotations will now load correctly in Visual Studio. They will still not restore or build until a reference to JetBrains.Annotations is added, or the check for it is disabled.

1.2.0 (2020-10-04)

New features

ReSharper.ExportAnnotations.Core is now distributed with a symbol package, thanks to SourceLink.
ReSharper.ExportAnnotations.Task checks for the presence of a package reference to JetBrains.Annotations, issuing a build-time error if it is missing. This functionality may be disabled by setting the CheckForJetBrainsAnnotationsPackageReference property to false.
ReSharper.ExportAnnotations.Task automatically updates the package reference to JetBrains.Annotations, ensuring that it is treated as a development dependency. This functionality may be disabled by setting the UpdateJetBrainsAnnotationsPackageReferencee property to false.
The name of the package containing the annotations DLL, for the purposes of the two features described above, may be specified via the JetBrainsAnnotationsPackageName property. When no name is specified, the default is JetBrains.Annotations.

Changes to existing features

ReSharper.ExportAnnotations.Task does no more strip annotations from compiled assemblies; instead, it invokes the Build target again without the JETBRAINS_ANNOTATIONS constant. This avoids the problems caused by the Mono.Cecil library not saving assemblies properly (see #2, #13, and jbevain/cecil#610 for details). Note that the --strip parameter of ExportAnnotations and the associated functionality remain unchanged, although they may be removed or deprecated in a future release.

Bugs fixed in this release

#2 - Stripping annotations also strips the signature away from strong-named assemblies
#13 - Stripping annotations also removes the portable PDB checksum

1.1.0 (2020-09-17)

New features

ExportAnnotations has a new --no-export option to skip the exporting phase entirely.

Changes to existing features

Ownership of the project changed from @rdeago to @Tenacom.

Bugs fixed in this release

#3 - ReSharper.ExportAnnotations.Task does not work with dotnet build and dotnet msbuild
#6 - Annotations are not stripped from executables

1.0.0 (2019-06-30) [DEPRECATED]

Initial release, deprecated because of ownership change.