This blog post is part of a series concerning Microsoft Code Contracts. For a complete series directory, please refer to the following list. Articles without a link will be published as they become available. Part 01 - Introduction
Part 02 - Preconditions
Part 03 - Postconditions
Part 04 - Object Invariants
Part 05 - Abstract Types and Interfaces
Part 06 - Assert, Assume, ForAll and Exists
Part 07 - Contract and Invariant Inheritance
Part 08 - Contract Reference Assemblies
Part 09 - Refactoring a Legacy Code Base
Part 10 - Writing a Custom Contract Runtime Class
Part 11 - Documenting Code Contracts
Part 12 - Command Line Tools
Part 13 - Contracts in Continuous Integration
Part 14 - A Chat with Microsoft's Code Contracts TeamMicrosoft Code Contracts have finally emerged from the Microsoft Research DevLabs into production. This is the first in a new blog series dedicated to spreading the good news about this amazing product. You may already know that Microsoft dumps billions of dollars into Research & Development every year, collaborating with academic, government and industry researchers all over the world to improve the platform. To be frank, this "culture of investment" is the main reason that I'm proud to call myself a .NET developer. Microsoft's deep level of investment is also attracting some of the best and brightest minds in software engineering to their research projects: another great reason for me to reply in kind, dedicating myself to mastering the platform. Read more: Developer Journey
Part 02 - Preconditions
Part 03 - Postconditions
Part 04 - Object Invariants
Part 05 - Abstract Types and Interfaces
Part 06 - Assert, Assume, ForAll and Exists
Part 07 - Contract and Invariant Inheritance
Part 08 - Contract Reference Assemblies
Part 09 - Refactoring a Legacy Code Base
Part 10 - Writing a Custom Contract Runtime Class
Part 11 - Documenting Code Contracts
Part 12 - Command Line Tools
Part 13 - Contracts in Continuous Integration
Part 14 - A Chat with Microsoft's Code Contracts TeamMicrosoft Code Contracts have finally emerged from the Microsoft Research DevLabs into production. This is the first in a new blog series dedicated to spreading the good news about this amazing product. You may already know that Microsoft dumps billions of dollars into Research & Development every year, collaborating with academic, government and industry researchers all over the world to improve the platform. To be frank, this "culture of investment" is the main reason that I'm proud to call myself a .NET developer. Microsoft's deep level of investment is also attracting some of the best and brightest minds in software engineering to their research projects: another great reason for me to reply in kind, dedicating myself to mastering the platform. Read more: Developer Journey