Home → Questions →

Code Contract support?

• Edit

micah

14 Jul, 2014 05:46 AM

Do the build servers have the Microsoft Code Contracts tools installed? Is it possible to install them? If not, what is the best solution for this sort of problem? Setup a build script that downloads the tools first then runs them as a after build?

Here is some information on running Microsoft Code Contracts on a build server:
http://stackoverflow.com/questions/3569108/microsoft-code-contracts...

If the best solution is to have them downloaded on build then I will probably make a NuGet package that contains the binaries and adds the necessary targets to make it all work.

1. Support Staff 1 Posted by Feodor Fitsner on 14 Jul, 2014 06:31 AM

   

   We'll deploy code contracts on build worker images.

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 14 Jul, 2014 10:07 AM

   

   It's been deployed to build worker images. Give it a try and let me know how it goes.

   • Edit

3. 3 Posted by micah on 14 Jul, 2014 04:49 PM

   

   Thanks! I'm heading to a 3 day conference this afternoon but I'll see if I can get it working before I leave. If not, then definitely later this week.

   • Edit

4. 4 Posted by micah on 15 Jul, 2014 01:39 AM

   

   Wow, that just worked out of the box. All I had to do was kick off another build (was previously failing).

   Thanks!

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 15 Jul, 2014 05:27 AM

   

   Great, thanks for the update!

   • Edit

6. 6 Posted by cyclotis04 on 29 Jul, 2015 06:23 PM

   

   Sorry to reopen an old topic, but can support be added for the Visual Studio 2015 environment? Code Contract support for VS 2015 just came out a couple weeks ago.

   I'm testing support here: https://ci.appveyor.com/project/dlras2/nugetpackagetemplate

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 29 Jul, 2015 08:22 PM

   

   Sure, I've added a new issue: https://github.com/appveyor/ci/issues/346

   • Edit

8. 8 Posted by cyclotis04 on 29 Jul, 2015 08:25 PM

   

   Thanks! Am I correct in my understanding that I will need to stay on the Visual Studio 2015 environment for the time being? (That is, the default one is not being updated in-place.)

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 29 Jul, 2015 08:27 PM

   

   We are bringing VS 2015 to Pro environment this week.

   • Edit

10. Support Staff 10 Posted by Feodor Fitsner on 29 Jul, 2015 11:24 PM

    

    Btw, you can install code contracts with this script: https://gist.github.com/FeodorFitsner/9769cb61790387005445

    • Edit

11. 11 Posted by cyclotis04 on 30 Jul, 2015 12:31 AM

    

    Thanks! That worked, though it added 20 minutes to my build time, so I'll keep an eye out for a resolution to that GitHub issue!

    • Edit

12. Support Staff 12 Posted by Feodor Fitsner on 10 Aug, 2015 04:25 AM

    

    It's been deployed, no need to install it during the build anymore.

    • Edit

13. 13 Posted by Eugene Auduchin... on 06 Jul, 2016 02:59 PM

    

    Please update the package to a newer release which fixes some serious bugs.
    https://github.com/Microsoft/CodeContracts/releases

    • Edit

14. Support Staff 14 Posted by Feodor Fitsner on 06 Jul, 2016 03:22 PM

    

    There is RC2. We'd prefer to wait for RTM before rolling it out to all build workers.

    Also, I've noticed there is a nuget package for Code Contracts - I'm wondering if this is an alternative way to install/use CC going forward?

    • Edit

15. 15 Posted by Eugene Auduchin... on 07 Jul, 2016 07:30 AM

    

    It's about a year now from the moment CodeContracts doesn't depend of VS2013 build tools anymore. We have to install msi on every build to work with 2015 build tools (which is needed for F# 4.0).
    Even though it is labeled as a pre-release, it fixes so much that it can be more stable the old release that is deployed now.

    And the NuGet package is indeed the the RC2.

    • Edit

16. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:07 AM.