Do not work with visual studio 2017 about codecontracts

[NameOfTheDragon]

I find it impossible to take a dependency on CodeContracts unless there is at the very minimum a roadmap for supporting VS2017 and future versions. This is far and away the best contract technology out there and I really want to be able to use it, but I can't have my entire development tool chain held back by it.

[yaakov-h]

Don’t.

[Ithalica]

Same. Any progress on this?

[SlyckLizzie]

Same thing here. Does not work with VS 2017.

[baSSiLL]

Unfortunately, Code Contracts still lack "official" support for VS 2017, even the latest sources.
However, you can get a limited support for VS 2017 and target runtimes v4.7.x by using CodeContracts.MSBuild Nuget package instead of Code Contracts installer.
https://www.nuget.org/packages/CodeContracts.MSBuild/
Limitations of the package:

• There's still no extension for VS 2017 adding Code Contracts pane into project properties editor. Therefore you need to add/edit project settings for Code Contracts manually in the project file.
• The package ships with the latest stable release of Code Contracts (v1.9.10714.3). So some bugs which have been fixed in sources and release candidates for v1.10 (https://github.com/Microsoft/CodeContracts/releases) are still there. For instance, be careful using closures in constructors as this may lead to NullReferenceException while checking preconditions (#191).

[Igorbek]

A new version 1.11-alpha of CodeContracts.MSBuild has been released with updated binaries (from the latest RC). It will be in alpha for 2 weeks. Enjoy!