Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m working on a LOB framework, with an SL and MVC frontend, WCF backend, and few service modules that run on the server. I’ve been looking at the Spec#, to see if it helps me in any way. The non-nullable types and the checked exceptions are very good by themselves, but I yet to find any specially good usage for the contracts. What are the pros, cons of using spec#?
Also, does the spec# license mean I cannot use spec# in a project which results in an application being sold to a paying customer?
Spec# is a research project. If you want similar features for production code you should look into Code Contracts.