Code Contracts Vs. Object Initializers (.net 4.0)

Posted by Mystagogue on Stack Overflow See other posts from Stack Overflow or by Mystagogue
Published on 2010-05-02T07:10:34Z Indexed on 2010/05/02 7:17 UTC
Read the original article Hit count: 299

Filed under:

code-contracts

|

object-initializers

|

.net-4.0

|

design-by-contract

At face value, it would seem that object initializers present a problem for .net 4.0 "code contracts", where normally the invariant should be established by the time the object constructor is finished. Presumably, however, object-initializers require properties to be set after construction is complete.

My question is if the invariants of "code contracts" are able to handle object initializers, "as if" the properties were set before the constructor completes? That would be very nice indeed!!

© Stack Overflow or respective owner

Related posts about code-contracts

Enabling XML-documentation for code contracts

as seen on ASP.net Weblogs - Search for 'ASP.net Weblogs'
One nice feature that code contracts offer is updating of code documentation. If you are using source code documenting features of Visual Studio then code contracts may automate some tasks you otherwise have to implement manually. In this posting I will show you some XML documentation files with documented… >>> More
Books on Code Contracts in C# 4.0

as seen on Stack Overflow - Search for 'Stack Overflow'
Altough I've known Code Contracts for some time, as I've used it a bit in Java, I would like to start using them in C#, now that they are part of C# 4.0. I am looking on learning material, books or vids. Altough tutorials are also welcome, I'd like to have something comprehensive to read, not the… >>> More
Code Contracts Preview: Interfaces

as seen on Dot net Slackers - Search for 'Dot net Slackers'
Dino Esposito continues his code contracts series and explains what mixins are. >>> More
Code Contracts Preview: Invariants

as seen on Dot net Slackers - Search for 'Dot net Slackers'
In this article, I'll go through the concept and implementation of class invariants as supported by the .NET Framework 4 Code Contracts API. >>> More
Understanding and Benefiting from Code Contracts in .NET 4.0

as seen on Internet.com - Search for 'Internet.com'
One of the fundamental programming challenges is managing state. Chances are you have written dozens and dozens of methods that at the beginning check that certain conditions are met, and that another set of conditions is met when the method returns. With Code Contracts in .NET 4.0, you can make things… >>> More

Related posts about object-initializers

Code Contracts Vs. Object Initializers (.net 4.0)

as seen on Stack Overflow - Search for 'Stack Overflow'
At face value, it would seem that object initializers present a problem for .net 4.0 "code contracts", where normally the invariant should be established by the time the object constructor is finished. Presumably, however, object-initializers require properties to be set after construction is complete… >>> More
Ninject with Object Initializers and LINQ

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm new to Ninject so what I'm trying may not even be possible but I wanted to ask. I free-handed the below so there may be typos. Let's say I have an interface: public interface IPerson { string FirstName { get; set; } string LastName { get; set;} string GetFullName(); } And a concrete: public… >>> More
Object initializers not working in List<T>.

as seen on Stack Overflow - Search for 'Stack Overflow'
List<Car> oUpdateCar = new List<Car>(); oUpdateCar.Add(new Car()); oUpdateCar[0].name = "Color"; oUpdateCar[0].value = "red"; oUpdateCar.Add(new Car()); oUpdateCar[1].name = "Speed"; oUpdateCar[1].value = "200"; The above code is working… >>> More
c# object initializer complexity. best practice

as seen on Stack Overflow - Search for 'Stack Overflow'
I was too excited when object initializer appeared in C#. MyClass a = new MyClass(); a.Field1 = Value1; a.Field2 = Value2; can be rewritten shorter: MyClass a = new MyClass { Field1 = Value1, Field2 = Value2 } Object initializer code is more obvious but when properties number come to dozen… >>> More
Initial capacity of collection types, i.e. Dictionary, List

as seen on Stack Overflow - Search for 'Stack Overflow'
Certain collection types in .Net have an optional "Initial Capacity" constructor param. i.e. Dictionary<string, string> something = new Dictionary<string,string>(20); List<string> anything = new List<string>(50); I can't seem to find what the default initial capacity is… >>> More