.NET 4.0's game-changing feature? Maybe contracts...

re: .NET 4.0's game-changing feature? Maybe contracts...

Alex James — Wed, 07 Jan 2009 20:02:26 GMT

...we can’t know whether the Nullable facet (i.e. a persistence constraint) applies in this context.

This distinction makes me think of the contract feature which is coming in .NET 4.0. In that in both situations we are really looking for more validation.

It also makes me wonder whether...

Nullable=”False”… but when exactly?

Meta-Me — Wed, 07 Jan 2009 05:52:32 GMT

If you look at the EDM and in particular the metadata it considers important, one thing is clear: Persistence

Nullable=”False”… but when exactly?

Meta-Me — Wed, 07 Jan 2009 05:28:51 GMT

If you look at the EDM and in particular the metadata it considers important, one thing is clear: Persistence

re: .NET 4.0's game-changing feature? Maybe contracts...

Chris Nahr — Wed, 12 Nov 2008 09:20:24 GMT

Update: Melitta Andersen has explained the current implementation of Code Contracts in greater detail on the BCL Team Blog:

blogs.msdn.com/.../introduction-to-code-contracts-melitta-andersen.aspx

Finally

Greg — Fri, 07 Nov 2008 17:56:23 GMT

Microsoft seems to be finally going for code quality with contracts, AKA beefed up asserts, and static analysis tools.

The cost of your code is not the initial development cost but the full cost over the lifecycle of the product. Looking at only initial development costs will greatly shorten the application's life-span and force you to spend much more money to rewrite/architect it in 2 years. We strive for at least a 5 year lifespan for our applications.

Reflective Perspective - Chris Alcock » The Morning Brew #218

Reflective Perspective - Chris Alcock » The Morning Brew #218 — Fri, 07 Nov 2008 08:36:57 GMT

Pingback from Reflective Perspective - Chris Alcock » The Morning Brew #218

re: .NET 4.0's game-changing feature? Maybe contracts...

Chris Nahr — Fri, 07 Nov 2008 07:11:36 GMT

I haven't watched this video yet but I'm also very excited about Code Contracts. I've wanted design by contract in C# ever since I wrote my first ArgumentNullException!

re: .NET 4.0's game-changing feature? Maybe contracts...

Pavel Minaev — Fri, 07 Nov 2008 03:57:11 GMT

> I'll be interested to see whether I can keep the pre-condition checks in the release build, just removing invariants and post-conditions etc.

It seems that's just what you'll get if you enable the conditional symbol for CodeContract, but don't run their assembly postprocessor.

re: .NET 4.0's game-changing feature? Maybe contracts...

Chris Martin — Fri, 07 Nov 2008 03:53:46 GMT

I agree! System.Diagnostics.Contracts is *life changing*!!!

GREAT stuff!

re: .NET 4.0's game-changing feature? Maybe contracts...

Charles Feduke — Thu, 06 Nov 2008 15:42:22 GMT

This will be great, I accomplish something similar using Umbrella's ValidationExtensionPoint but something that can hint unit tests, documentation, as well as run time validation would be ideal.

re: .NET 4.0's game-changing feature? Maybe contracts...

Brian — Thu, 06 Nov 2008 12:02:03 GMT

This session has additional details: channel9.msdn.com/.../PC49

Looks very interesting.

re: .NET 4.0's game-changing feature? Maybe contracts...

Marc Gravell — Thu, 06 Nov 2008 09:54:20 GMT

Watching it. Loving it. Cheers.