(If whoever thought my comment needed downvoting would like to explain why -- because it's too obvious? because it's wrong? because there's nothing at all wrong with a major software vendor making totally false and unreasonable claims in their promotional materials? -- then I am, seriously although not literally, all ears.)
Poor Eiffel; its doom was to lead the way, and get picked apart by its children. Maybe if it hadn't looked like Pascal it might have done better. That said, I'm really surprised that design by contract hasn't been incorporated more widely, before now.
It all depends on how you define "quality".
And your down-votes could be attributed to the topic of the thread. Anything that casts doubt over Microsoft's One True Way is not welcome in certain message threads.
Code Contracts provide a language-agnostic way to express coding assumptions in .NET programs. The contracts take the form of pre-conditions, post-conditions, and object invariants. Contracts act as checked documentation of your external and internal APIs.
http://msdn.microsoft.com/en-us/devlabs/dd491992.aspx