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.
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?
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?
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..
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.
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...
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.