Basic code contracts for public facing API

[alexsimply]

This adds basic postconditions for Mock creation.

See issue: Add support for code contracts

[kzu]

All of these code contracts properties seem to be duplicated in Debug/Release configurations. It's better to put them outside, in a new property group specific for this feature, and only leave in Debug/Release the deltas.

[varon]

This settings are usually configured by means of a GUI (an extra page on the project properties) inside Visual Studio. I'm unsure as to what the configuration behaviour would be should they be grouped up in another manner.

While we can reduce code duplication by using a higher level property group, it's worth noting that these settings are independent of each other, and despite their verbosity, do follow the existing project standard of having each configuration contain it's own settings, as seen in properties like and .

[kzu]

I don't like the duplication. And we're most certainly not going to change
any of those settings in the foreseeable future from VS.

And since it's plain msbuild, the effect of changing the grouping is none.

/kzu from mobile
On Feb 21, 2014 7:29 AM, "varon" notifications@github.com wrote:

This settings are usually configured by means of a GUI (an extra page on
the project properties) inside Visual Studio. I'm unsure as to what the
configuration behaviour would be should they be grouped up in another
manner.

While we can reduce code duplication by using a higher level property
group, it's worth noting that these settings are independent of each other,
and despite their verbosity, do follow the existing project standard of
having each configuration contain it's own settings, as seen in properties
like and .

Reply to this email directly or view it on GitHubhttps://github.com//pull/95#issuecomment-35717546
.

[kzu]

I'll fix the XML later.

[kzu]

Hi @APeel , looks like these changes weren't #ifdef'ed and we've a broken build for SL now :(

Any chance you can look at that?

[varon]

(on behalf of @APeel)
We're no longer using Moq here, so we're not going to look into it.
Should be simple to fix.
Otherwise just revert it, although it seems like a pretty popular issue.