Cerulean series release 1

3.5.512

• Separate NuGet packages altcover.dotnet and altcover.global that contain the command-line tool functionality (only) for .net core as a CLI tool and as a .net core global tool respectively
• [BREAKING] dotnet test integration - all names have been prefixed with AltCover to avoid collisions
• [BREAKING] dotnet test integration - | is used as the separator character for lists rather than ; as the latter causes problems in the command-line context
• Extended the ConvertTo-Cobertura and ConvertTo-Lcov cmdlets
• ConvertTo-XDocument and ConvertTo-XmlDocument to interconvert in the object pipeline
• ConvertTo-NCover to take OpenCover format to classic NCover

Cerulean series pre-release

3.5.500-pre

• Reduce the amount of unnecessary infrastructure runtime code in the .nupkg that bloated the 3.0.488-490 release
• Expose the LCov and Cobertura output formatters as simple cmdlets ConvertTo-Cobertura and ConvertTo-Lcov to take OpenCover or NCover format input.
• Minor adjustments to the Invoke-AltCover cmdlet based on PowerShell guidelines -- plural argument names made singular with backwards-compatible aliases

Caba series release 12 re-spin

3.0.490

• Invoke-Altcover cmdlets for both Windows PowerShell and PowerShell Core
• coverlet-style dotnet test integration
• [BUGFIX] -- Possible branch instrumentation failure when filtering is applied.

Caba series release 11

3.0.475

• Fine tune the speed-up in data collection (marginal improvements only)
• [BUGFIX] -- some corner cases for nested functions (including uses of generics) were not being detected for purposes of exclusion by containing function
• [BUGFIX] -- Issue #17 : restore intended behaviour when no arguments supplied
• [BUGFIX] -- Issue #18 : protect against certain degenerate cases when looking for branch coverage
• other minor build process changes

Caba series release 10

3.0.466

• Support for starting/pausing/resuming coverage collection during operation -- see https://github.com/SteveGilham/altcover/wiki/Pause%E2%95%B1Resume-and-the-Control-File
• Major speed-up in data collection by reducing the amount of synchronization being done while writing data to file -- this means significant reductions in the time taken for instrumented code to execute
• Support for excluding C#7.0 local functions by excluding the enclosing method
• Add CRAP (Change Risk Anti-Patterns) score to methods (and min/max values to summaries) in --opencover format and runner/Collect mode
• [BUGFIX] -- using dotnet AltCover.dll to instrument a .net core project using F# could fail when rewriting the .deps.json file.
• [BUGFIX] -- not all branches were being tallied for certain complex F# match expressions

Caba series release 9

3.0.455

• -o|outputFile option in runner mode (parameter OutputFile for the AltCover.Collect task) to allow the default report for the current dataset to be written to a new file, rather than updating/accumulating in the file specified at instrumentation time.
• Some refactoring and adjustments to the build processes
• [BUGFIX] -- handle and signal exceptions in the visit recording, rather than potentially just locking up or silently failing
• [BUGFIX] -- ensure that more of the IDisposable objects generated, primarily the ones that can lock the assemblies under instrumentation, are promptly disposed.

Caba series Release 8

3.0.444

• [BUGFIX] for -c|callContext option -- generate valid IL where the function being tracked completes with a tail call
• [BUGFIX] for -c|callContext option -- generate valid IL where the function being tracked contains a branch directly to a return instruction
• -c|cobertura option in runner mode (parameter Cobertura for the AltCover.Collect task) -- Cobertura format output to the given file name (more complete for OpenCover format coverage gathering than NCover, inevitably)
• Signal failure explicitly for -t|threshold violations, as well as through the return code

Caba series Release 7

3.0.433

• -t|threshold option in runner mode (parameter Threshold for the AltCover.Collect task) to fail the build (non-zero return code or MSBuild error state) if coverage falls below the specified percentage
• [BUGFIX] -- Parameters weren't being re-initialised on the second or subsequent use of the MSBuild tasks, leading to failures about arguments being specified more than once (Issue #10)
• [BUGFIX] -- ArgumentNullException when relaying output from a launched process: filter null/empty messages
• FIXED AGAIN : reinstate earlier change [f61f951] to write .mdb out for .mdb in (and pdb out for pdb in) -- at least on .net core and full .net (long story)
• Moving some of the unit tests to XUnit for reasons related to the above

Caba series Release 6

3.0.422

• [BUGFIX] -- Cecil resolves type dependencies by looking relative to the current working directory, no matter where it's actually writing the file : so work in the target directory wheil we are writing
• Also, just in case, ensure we process files from the depended-upon first, up the dependency chain (assumes no dependency cycles).
• Give feedback of what is written where and when.

Caba series Release 5

3.0.416

• Exclude constructors on compiler generated types as being simply noise -- they will be exercised if you use any of the real code they represent, so nothing of importance is lost
• C# compiler generated types for lambdas, async/await and yield return are mapped to their containing methods for the purpose of filtering by method name or method level attributes
• F# compiler generated types for lambdas, nested named functions and computation expressions are mapped to their containing methods (and their containing methods, if relevant) for the purpose of filtering by method name or method level attributes so that a filter at any level will be picked up by deeply nested inner functions
• Even more feedback on error, including logging exception detail to file.
• [BUGFIX] Mono.Cecil can give ArgumentException when given an arbitrary file input (while detecting which files are instrumentable assemblies); handle that case