Comments (7)
I think that for some people the CC Editor Extensions are very important. I would not hold off on releasing CC for VS 2015 over it but it should at least be in the next milestone. @Daniel-Svensson is at least one user that finds it important and I also would like to see that functionality.
from codecontracts.
@aarondandy I'm not saying that CC Editor Extension is not important, I'm saying that we can split this into two releases. And, actually, Code Contracts itself and CC Editor Extensions are two different VSIX packages anyway. I'm just saying that this is two separate milestones that could be accomplished in parallel.
from codecontracts.
#66 adds editor support for Visual Studio 2013, and a clear stepping stone for providing support for 2015 in a follow-up pull request. Initially I worked to modify the shared code to support both 2010-2013 and 2015, but the differences in 2015 turned out to be sufficiently complex that I'm planning to instead split the 2015-specific details into their own directory in the source tree. This would not affect our ability to ship a single VSIX that supports all versions of Visual Studio.
tl;dr Editor extension support for 2013 is already implemented (#66). 2015 is in progress, but I can't be certain when it will be finished.
from codecontracts.
@sharwell As I mentioned already, I'm not arguing against CC Editor Extension, I'm just trying separate the concerns. I've created separate milestone (https://github.com/Microsoft/CodeContracts/milestones/CCEditorExtensionVS2015) and anyone can create the same ticket for tracking this milestone progress.
Editor Extension has different deliverables and I just can't understand why we should mix them up. We can do everything in parallel and deliver great experience in timely manner.
Those tools was always released separately and I don't think that for the very first release we should mix them up.
from codecontracts.
❓ BTW @sharwell could you suggest what changes are required to get cccheck/ccrewrite integration with VS2015?
from codecontracts.
In my previous comment, I was simply stating the current state of the items I was working on. Regarding the milestones, I would probably put all the issues into a single milestone initially. Then if one set of features reached completion and the other set still had significant work left, I'd split it at that point by simply moving all the remaining open issues from the first milestone to a new one.
The biggest issue for my code is ccrewrite functionality. We use Contract.Requires<TException>
, which means without ccrewrite support Visual Studio 2015 is completely unusable for our project. I have not yet tested to see what is required, but I'm hoping to start testing this on Sunday (by "this", I mean the several open pull requests which are intended to solve some or all of the currently known problems).
I'm also thinking it would be a good idea to create a gitter room for the project, even if it means changing the room and losing history when the project moves to a new GitHub organization.
from codecontracts.
Understood. You can pull my fix ( #74 ) and check is it working for you. If you have special test cases that you would like to test, just put them as a comment for PR.
I'll be talking with @mike-barnett tomorrow and we'll review my PR's (and other changes that I'm working on, including the fix for #38).
I've created a gitter chat room: https://gitter.im/Microsoft/CodeContracts
from codecontracts.
Related Issues (20)
- Rewriter produces incorrect debug information for async methods in PDB file HOT 1
- Removing Code Contracts from a project when upgrading to VS2017 HOT 1
- Rosalyn Code Analyzer for Code Contracts Usage HOT 4
- .NET Framework 4.7 BCL Contracts
- ccrewrite aborted due to metadata errors (Xamarin or VS2017 15.2 related?)
- StackOverflowException in cccheck.exe
- IDictionary contracts and boxing HOT 2
- Postcondition missing from StringBuilder.AppendFormat(IFormatProvider, string, object)
- How to enable "perform runtime contract checking" in Visual Studio 2017? HOT 19
- Do not work with visual studio 2017 HOT 6
- COMException (0x80004005)
- Build with CodeContracts fails with dotnet build
- Document for the implementation/source code?
- Another NullReferenceException with closure in constructor
- VS2017 path to sn.exe is wrong
- Reading assembly 'Unity.Abstractions' generate System.OutOfMemoryException HOT 1
- BadImageFormatException with enabled runtime checking
- Rewrite tool introduce bugs in local functions
- Preconditions with non-interger decimals are broken
- Enable contracts in VS Community 2019
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from codecontracts.