These are chat archives for Microsoft/CodeContracts

6th
Jul 2015
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:10

@sharwell Sounds awesome! Congrads.

BTW I didn't get exactly, what did you mean by "or we decide to not ship the VSIX as part of the MSI..". I though that Editor extension was released separately from main Code Contracts msi...

BTW, I have a fix for remaining part for VS2015!
Sam Harwell
@sharwell
Jul 06 2015 23:10
Hey! :D
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:10
Will push a PR later today!
Sam Harwell
@sharwell
Jul 06 2015 23:11
I'm trying to figure out the build process for the VSIX
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:11
:)))
Sam Harwell
@sharwell
Jul 06 2015 23:11
it's the remaining part for this side of things
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:11
it is for ccrewrite stuff, to deal with non-capturing lambda...
Sam Harwell
@sharwell
Jul 06 2015 23:12
yes
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:12
fix was required because roslyn-based compiler uses new schema for non-capturing lambda caching...
Sam Harwell
@sharwell
Jul 06 2015 23:12
but if I fix the build process for the editor extensions, the VS 2015 update will really be a full-fledged 2015 update from the start
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:12
BTW, I've reformatted the code for "Foxtrot". I tried to figured it out without it, but finally I decided to reformat it and move the types into separate files, because it was so painful to debug and reason about the code
Sam Harwell
@sharwell
Jul 06 2015 23:13
hopefully as its own separate pull request?
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:13

but if I fix the build process for the editor extensions, the VS 2015 update will really be a full-fledged 2015 update from the start

I just don't know... That's why I thought to keep this stuff as before

hopefully as its own separate pull request?

Yep

Sam Harwell
@sharwell
Jul 06 2015 23:14
How do you build this for a release?
(currently)
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:15
build.bat VERNUM
it creates all required stuff
Sam Harwell
@sharwell
Jul 06 2015 23:15
k
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:15
I need to sign it via MS Stuff if we want to have one final release that would be published by MS
Sam Harwell
@sharwell
Jul 06 2015 23:15
what should I put for vernum to see if it's working?
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:16
my fix? or what exactly you want to test?
Sam Harwell
@sharwell
Jul 06 2015 23:16
no, my stuff in #66
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:17
oh... I have no idea :(
Sam Harwell
@sharwell
Jul 06 2015 23:18
what VERNUM do you put if you just want to test the current state locally?
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:20
For all rewriter stuff there is a reasonable test coverage...
Or what exactly do you mean by VERNUM?:)
Sam Harwell
@sharwell
Jul 06 2015 23:24
I found this on the readme:
buildCC 1.8.10107.10
Sergey Teplyakov
@SergeyTeplyakov
Jul 06 2015 23:39
BTW, Mike described me what the versioning schema is using by this tool... We can continue to use it (at least for this release).
Sam Harwell
@sharwell
Jul 06 2015 23:52
so it looks like buildCC does not build the editor extensions
wait, it might... need to check one more thing