Future plans for Code Contracts

[mike-barnett]

This issue is meant to provide a single place where we can keep people notified about the status of the Code Contracts project. We (Microsoft) now have some resources and will do the work (in conjunction with the community of course) to update the sources so the tools will work in VS2015. After that, we are looking to transition the repo outside of the Microsoft organization in GitHub and turn ownership over to any community members that are interested.

As far as we are aware, the current work items are:

1. Updating the rewriter to understand the new Roslyn code-generation patterns for iterators/async.
2. Updating the Visual Studio integration so that the Code Contracts pane appears in the project properties window.
3. Fixing some other missing files, etc.

Separately, there is a Roslyn discussion (dotnet/roslyn#119) about adding contracts to a future version of C#.

[hubuk]

There were some work done by the community:
Point 1. is partially addressed by #52.
Point 2. is resolved by #36.
Missing repository content for point 3 is listed in #6.

[vmelamed]

This is great news! The only obstacle for me to start using VS2015(RC) are the code contracts. Currently almost all my projects use it. Can't wait for the release.

[yaakov-h]

... we are looking to transition the repo outside of the Microsoft organization in GitHub and turn ownership over to any community members that are interested.

What's the reasoning for this?

[krk]

Possibly related to the "next step" for code contracts being stated as "re-architecturing to integrate Z3" in this document (CodeContracts.pptx).