Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sergey Teplyakov
    @SergeyTeplyakov
    @yaakov-h Merged your PR! Great job!
    Yaakov
    @yaakov-h
    Thanks @SergeyTeplyakov. Hopefully I'll be able to do a full test with the next RC now.
    Yaakov
    @yaakov-h
    @SergeyTeplyakov Do you have a timeline for RC2 / 1.10 stable?
    Sergey Teplyakov
    @SergeyTeplyakov
    I'm almost done with #365 and this is the main bug that I want to fix
    I think we should fix #13 and good to go with RC2
    Yaakov
    @yaakov-h
    looks like for #13 we just need build\DotNet.CodeContracts.props containing DontImportCodeContracts, and build\DotNet.CodeContracts.targets which then imports MSBuild\$(VisualStudioVersion)\Microsoft.CodeContracts.targets
    Sergey Teplyakov
    @SergeyTeplyakov
    Sounds like not a very complicated task...
    Sergey Teplyakov
    @SergeyTeplyakov
    Ok, guys. We have 1 year Pro subscription on AppVeyor!!
    Now I can turn all the tests back!
    Yaakov
    @yaakov-h
    \o/
    Hubert Bukowski
    @hubuk
    This message was deleted
    Hubert Bukowski
    @hubuk
    Did you read Joe Duffy's article about error model in Midori?
    http://joeduffyblog.com/2016/02/07/the-error-model/
    There is a lot about Microsoft's approach to contracts. With a few words on why Code Contracts were dropped for this system.
    Yaakov
    @yaakov-h
    interesting stuff, that
    Onur Gumus
    @OnurGumus
    with new newtonsoft.json I am getting below error:
    All packages listed in C:\Users\onur.gumus\Documents\Projects\PIWorks.Web\PIWorks.Web.WebAPI.Client\packages.config are already installed.
    3> elapsed time: 1183,8611ms
    3> Reading assembly 'Newtonsoft.Json' from 'C:\Users\onur.gumus\Documents\Projects\PIWorks.Web\packages\Newtonsoft.Json.8.0.2\lib\portable-net40+sl5+wp80+win8+wpa81\Newtonsoft.Json.dll' resulted in errors.
    3> Could not resolve type reference: [mscorlib]System.IConvertible.
    3> Could not resolve type reference: [mscorlib]System.TypeCode.
    3> Could not resolve member reference: System.IConvertible::GetTypeCode.
    3> Could not resolve member reference: System.IConvertible::ToBoolean.
    3> Could not resolve member reference: System.IConvertible::ToChar.
    3> Could not resolve member reference: System.IConvertible::ToSByte.
    3> Could not resolve member reference: System.IConvertible::ToByte.
    3> Could not resolve member reference: System.IConvertible::ToInt16.
    3> Could not resolve member reference: System.IConvertible::ToUInt16.
    3> Could not resolve member reference: System.IConvertible::ToInt32.
    3> Could not resolve member reference: System.IConvertible::ToUInt32.
    3> Could not resolve member reference: System.IConvertible::ToInt64.
    3> Could not resolve member reference: System.IConvertible::ToUInt64.
    3> Could not resolve member reference: System.IConvertible::ToSingle.
    3> Could not resolve member reference: System.IConvertible::ToDouble.
    3> Could not resolve member reference: System.IConvertible::ToDecimal.
    3> Could not resolve member reference: System.IConvertible::ToDateTime.
    3> Could not resolve member reference: System.IConvertible::ToType.
    3>ccrewrite : error : Rewrite aborted due to metadata errors. Check output window
    Yaakov
    @yaakov-h
    @SergeyTeplyakov Any ETA for RC2?
    Sergey Teplyakov
    @SergeyTeplyakov
    @yaakov-h Let's see what we need to fix before.
    Jeroen Mostert
    @jeroen-mostert
    If I've modified and rebuilt a contract reference assembly shipped with CC, is there an easy way to test it in my project? Neither the extra contract library path nor copying it in my project directory itself seem to override the existing version.
    Jeroen Mostert
    @jeroen-mostert
    I ended up solving this by copying the entire toolchain to somewhere else, creating a junction for the \Contracts directory to my local build, and editing the project file to use a different CodeContractsInstallDir. There's no kill like overkill!
    (Still, if there's an easier or better way, and there likely is, I'm all ears. :-) )
    Yaakov
    @yaakov-h
    @SergeyTeplyakov well #359 is still outstanding (among others) :smie
    :smile:
    any idea about #385 though? I'm not even sure where to begin looking.
    normandocarvalho
    @normandocarvalho
    Hi everrybody, I have a question. Is it possible to write a contract.ensure to verify external API?
    Kerem
    @krk
    Is this project supported by Microsoft at any rate?
    Lelouch lkytal
    @lkytal
    When will the next release come?
    Yaakov
    @yaakov-h
    @SergeyTeplyakov What's happening? This project going dead as a doornail for extended periods doesn't exactly install confidence in consumers...
    Jeroen Mostert
    @jeroen-mostert
    It is rather annoying that MS seems neither willing to dedicate resources to it, nor make a firm statement on what kind of resources it wants to dedicate. Making it open source won't help either if there's no resources for merges. Do MS teams even use CC themselves? If so, what do they think about it?
    Veikko Eeva
    @veikkoeeva

    Mm, maybe it is only fair to point out that in many sources, e.g. at https://blogs.msdn.microsoft.com/dotnet/2015/02/03/coreclr-is-now-open-source/

    I had a look and notice most of the Code Contracts are commented out. Will this be fixed at some point?
    No, we currently don't have plans to bring in code contracts.

    https://github.com/aspnet/Home/wiki/Engineering-guidelines

    Use Debug.Assert() to assert a condition in the code. Do not use Code Contracts (e.g. Contract.Assert).

    I remember reading on some research papers as to why pre- and post-conditions are somewhat a problematic thing in production code. Basically, I think, verifying is problematic. For that maybe a promising direction is dependent types and considering especially Microsoft perhaps F*.
    erisco
    @erisco
    testing 123
    anyone out there?
    Antão Almada
    @aalmada
    :(
    Eyal Solnik
    @eyalsk
    @veikkoeeva Yeah, I read here in the comments that they aren't planning to use CodeContracts at all, I've been using CodeContracts since its early releases and I'm ditching it in my own projects , mainly because development is slow but hopefully with C# 8 or later, they will add contracts to the language. :)
    Michael Caron
    @mrcaron
    Is this still pretty active? I just saw Miguel use a Contracts namespace in Xamarin Studio during Evolve keynote this morning. It looked like it was part of Mono Foundation rather than a System* namespace though. Are they related?
    Antão Almada
    @aalmada
    To my best knowledge, Xamarin Studio does not support Code Contracts. It requires special tools after compilation. You can vote for this feature at https://xamarin.uservoice.com/forums/144858-xamarin-platform-suggestions/suggestions/7057541-support-for-invoking-code-contracts-tools
    Aaron Dandy
    @aarondandy
    Somebody else was asking about the activity in this project on github: Microsoft/CodeContracts#409
    yagami light
    @mtgstarts_twitter
    anyone here?
    Yaakov
    @yaakov-h
    maaaaybe
    Vytautas Tumas
    @Tapanito
    Hello,
    Does anyone know whether CodeContracts are supported by the IntelliTest generator? That is does IntelliTest recognize code contracts, thus skips redundant test generation?
    HarryGifford
    @HarryGifford
    @Tapanito not as of yet unfortunately.
    Sergey Mozhaykin
    @smozhaykin
    Hello,
    How can I use code contracts with obfuscator? I obfuscate code on AfterCompile step, but after it ccrewriter fails. Is there any way to execute it after ccrewriter?
    Nathanael Gethers
    @DIGnmg
    Hello all! I have a quick question. Has anyone been able to use Code Contracts on a parallels machine? I am on a mac with VS running on parallels. I cant seem to build anything and wasnt sure if its bc the .exe is on the PC side and all my source code is in the mac drive. Any ideas?
    Sergey Teplyakov
    @SergeyTeplyakov
    @smozhaykin I think you can do this by using some MSBuild magine. Technically, both of them (obfuscator and ccrewrite) are taking dll and provide a dll. So with some tools like Fake it should be trivial, but I'm not sure how to achieve this using MsBuild.
    @DIGnmg Never used parallels, so can't provide any feedback. But can you build regular stuff?
    Nathanael Gethers
    @DIGnmg
    @SergeyTeplyakov yes i can build other things. I moved the source code to my VM and it builds fine.
    Jeroen Mostert
    @jeroen-mostert
    I'm trying to use CC on a .NET Core project (don't laugh). I know CoreCLR itself doesn't use it, and VS has no support etc., that's alright. My main stumbling block is that I can't get ccrewrite to emit assemblies .NET Core likes. In particular, it futzes up the metadata references so that (e.g.) a reference to System.Private.CoreLib is included for System.Object. Is this something I could fix with some elbow grease or is it intrinsically hopeless?
    Jeroen Mostert
    @jeroen-mostert
    I'm going to go with "intrinsically hopeless". This is buried in the bowels of CCI somewhere and I really don't feel like untangling that mess. Realistically, a Roslyn extension should take care of rewriting and ccrewrite could then be left for everything Roslyn can't handle, but that project is a little out of scope at the moment. For now, I'll simply give up on rewriting and migrate the codebase to if-then-throw.