These are chat archives for Microsoft/CodeContracts

21st
Jul 2015
Sergey Teplyakov
@SergeyTeplyakov
Jul 21 2015 16:16
New version of Code Contracts was published on VS Gallery: https://visualstudiogallery.msdn.microsoft.com/1ec7db13-3363-46c9-851f-1ce455f66970
Sam Harwell
@sharwell
Jul 21 2015 16:20
:+1:
Sergey Teplyakov
@SergeyTeplyakov
Jul 21 2015 16:44
Thanks a lot for everyone for your help!
jbcutting
@jbcutting
Jul 21 2015 19:45
Is the issue with code contracts output not showing in the error list in VS2015 (#137) not going to be addressed for the VS2015 release? Without that, users aren't going to see the output for missing contracts unless they happen to go to the output window.
That also includes output for static analysis failures.
Sam Harwell
@sharwell
Jul 21 2015 20:18
@jbcutting it was less important an issue than getting ccrewrite working
We needed to get an initial release out the door ASAP so builds were unblocked
Issue #137 and a few others are important next steps
jbcutting
@jbcutting
Jul 21 2015 20:19
I get that, but it does seem like releasing something that doesn't give expected warnings for something people rely on (static analysis) could cause problems for people.
Also, I don't have repro steps yet, but the editor extension is still crashing regularly in VS2015... I've been having to disable it.
Sam Harwell
@sharwell
Jul 21 2015 20:21
Re crashing: Look at the Output window for the "Code Contracts Editor Extensions" pane and you'll see stack traces. I've found 2 so far; they result in an error dialog but visual studio keeps running.
If you have a case where visual studio actually crashes, that would be more important to address immediately.
jbcutting
@jbcutting
Jul 21 2015 20:22
For the analysis, I can at least tell my team to pay attention to the output window. If we're not including that as a known issue, others may upgrade and miss static analysis issues because they have no knowledge that the output is broken.
I'll check. I agree that a VS crash would be worse, but why did the editor extension update get released if it hasn't been thoroughly tested in VS2015?
Sam Harwell
@sharwell
Jul 21 2015 20:23
The ccrewrite work for 2015 was almost all @SergeyTeplyakov (with no time for any editor features at all). The 2013 and 2015 support for the editor extensions was almost entirely me, and I know it has a long way to go. Keep in mind that I saw the code for the first time earlier this summer and it's just something I do in my spare time (evenings/weekends).
The installer work for 2015 and updated contracts were done by a few other members of the community, including @hubuk and @tom-englert

why did the editor extension update get released if it hasn't been thoroughly tested in VS2015?

Mostly because VS 2015 didn't exist at the time.

jbcutting
@jbcutting
Jul 21 2015 20:25
Regarding the editor extension - I understand that. Please understand that I'm not trying to devalue the work you did here - I'm glad that you did it. However, if it hasn't been verified in VS2015, perhaps it shouldn't be listed as being supported there in the release..
Sam Harwell
@sharwell
Jul 21 2015 20:26
The wording seems... suboptimal. But I guess it works.
jbcutting
@jbcutting
Jul 21 2015 20:26
Others will download and install it, expecting it to work in VS2015, and then the negative reviews will start racking up due to the crashes..
Sam Harwell
@sharwell
Jul 21 2015 20:26
It's better than it was in 2013 (always crashed for everyone every time)
jbcutting
@jbcutting
Jul 21 2015 20:27
Agreed, but at least it wasn't listed as being supported in VS2013
Sam Harwell
@sharwell
Jul 21 2015 20:27
Here's my recommendation:
  1. File bug reports when you can
  2. Add comments to issues reported by other people that are affecting you, to help us triage the most important items in the time we have available
  3. (Bonus points) Help us figure out why it's not working and fix it :smile:
jbcutting
@jbcutting
Jul 21 2015 20:28
I at least know the issues and can disable the editor extension and tell my team to look at the output window for the other issue. But everyone getting these from the VS gallery has no knowledge of those and nobody's telling them the issues.
Sam Harwell
@sharwell
Jul 21 2015 20:29
Messaging is something we can (hopefully) work on after the project is turned over to the community. I'm not sure what the time frame is for that or exactly how it will work.
jbcutting
@jbcutting
Jul 21 2015 20:29
It's not even really about me at this point... I know the issues and can work around them. I'm concerned for all the people who are going to go download these with no knowledge and lose time figuring them out..
As a former developer at Microsoft myself, I can say that this is the kind of stuff MS usually at least communicates so people are aware...
Sam Harwell
@sharwell
Jul 21 2015 20:31
Can you get me a list of the issues you would consider "essential" for a successful release? It might be short enough that we can get it done in a reasonably short period of time.
jbcutting
@jbcutting
Jul 21 2015 20:33
For CC itself, there's just the one that I know of since it hides important output from users. For the editor extension, I'd say it's just stopping the regular crash. But paramount over fixing either, I think the big known issues should be listed on the VS gallery posts.
Sam Harwell
@sharwell
Jul 21 2015 23:14
@jbcutting Found them. They're in the Task List (View → Task List)