October 2nd, 2015
This is an stabilization release, with several bug fixes. There is only one known bug, and the analyzer that is affected is disabled.
We will continue to focus on stabilization until 1.0.0 is ready.
Any new fixes will end up on the master branch.
New analyzers and fixers will continue to go on the vnext branch and will not be on our 1.0.0 release.
This release is still targetting the final version of Visual Studio 2015 (RTM, version 14.0.23107.0 D14REL), as will the next ones. This release targets the 1.0.0 version of the Roslyn API (Microsoft.CodeAnalysis.*).
This release will not work on pre-release versions of VS 2015.
There are no new analyzers or code fixes in this release.
When the analyzer/code fix impacts the resulting code we disable it by default, you need to enable those that are disabled to be able to use them.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
For a list of what worked on see the corresponding milestone and the detailed changelog. For the commits, see the full changelog.
August 19th, 2015
This release is still targetting the final version of Visual Studio 2015 (RTM, version 14.0.23107.0 D14REL), as will the next ones. This release targets the 1.0.0 version of the Roslyn API (Microsoft.CodeAnalysis.*).
This release will not work on pre-release versions of VS 2015.
This is an stabilization release, with several bug fixes. There is only one known bug, and the analyzer that is affected is disabled.
We will continue to focus on stabilization until 1.0.0 is ready.
Any new fixes will end up on the master branch.
New analyzers and fixers will continue to go on the vnext branch and will not be on our 1.0.0 release.
When the analyzer/code fix impacts the resulting code we disable it by default, you need to enable those that are disabled to be able to use them.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
For a list of what worked on see the corresponding milestone.
July 22nd, 2015
This release is the first one targeting the final version of Visual Studio 2015 (RTM, version 14.0.23107.0 D14REL). This release targets the 1.0.0 version of the Roslyn API (Microsoft.CodeAnalysis.*).
The nuget package format has been updated from RC to RTM and this release will not work on pre-release versions of VS 2015.
From now on we will focus on stabilization and performance. There are only 3 known bugs, and we have some performance work to do. This work will end up on the master branch.
New analyzers and fixers will now go to a vnext branch and will not be on our 1.0.0 release.
When the analyzer/code fix impacts the resulting code we disable it by default, you need to enable those that are disabled to be able to use them.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
For a list of what worked on see the corresponding milestone.
July 3rd, 2015
This release is still targeting Visual Studio 2015 RC, as we wait for the RTM on July 20th. The only bug present at the time is one that is due to a bug on Roslyn itself. This is most likely our last pre-release as we prepare for the VS RTM. The next release will most likely be 1.0.0.
When the analyzer/code fix impacts the resulting code we disable it by default, you need to enable those that are disabled to be able to use them.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
For a list of what worked on see the corresponding milestone.
May 31st, 2015
This release is updated to target the 1.0.0-rc2 Roslyn Analyzers API, which works with Visual Studio 2015 RC. We have also focuses heavily on fixing all our bugs. The only bugs left are one that is due to a bug on Roslyn itself and a recently discovered one. We have been working hard on making CodeCracker more resilient. We started working on fix all tests, and have increased the code coverage, which was already high. It should continue to increase in the next releases. In this release we have surpassed the 1000 tests mark for the C# project alone!
When the analyzer/code fix impacts the resulting code we disable it by default, you need to enable those that are disabled to be able to use them.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
For a list of what worked on see the corresponding milestone.
Apr 25th, 2015
This release still targets the 1.0.0-rc1 Roslyn Analyzers API, which works with Visual Studio 2015 CTP 6. We have updated CodeCracker in this release so it does not raise diagnostics on generated code. See issue 260 for more information on this subject. We have also focuses heavily on fixing all our bugs, only one remains, and it is due to a bug on Roslyn itself.
The above analyzer is disabled by default, you need to enable it to be able to use it.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
For a list of what worked on see the corresponding milestone.
Mar 3rd, 2015
This release targets the 1.0.0-rc1 Roslyn Analyzers API, which works with Visual Studio 2015 CTP 6. This release we also started taking better care of how code fix work when working on the “fix all” scenarios, when the whole document, project or solution is fixed.
All the above analyzers are disabled by default, you need to enable them to be able to use them.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
For a list of what worked on see the corresponding milestone.
Jan 31st, 2015
This release targets the 1.0.0.0-beta2 Roslyn Analyzers API, which works with Visual Studio 2015 CTP 5. This is our first release with Visual Basic.
All the above analyzers are disabled by default, you need to enable them to be able to use them.
As usual, you should go to Nuget (C#, VB) to get the packages or download the extension on the Visual Studio Extensions Gallery (C#, VB).
Dec 15, 2014
Nov 12, 2014