<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Annotations on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/annotations/</link><description>Recent content in Annotations on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 05 Jun 2011 23:55:00 +0200</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/annotations/index.xml" rel="self" type="application/rss+xml"/><item><title>Let ReSharper and Code Contracts work together</title><link>http://blog.marko-apfel.de/posts/let-resharper-and-code-contracts-work-together/</link><pubDate>Sun, 05 Jun 2011 23:55:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/let-resharper-and-code-contracts-work-together/</guid><description>&lt;p&gt;&lt;em&gt;ReSharper&lt;/em&gt; by default does not recognize &lt;code&gt;Contract.Requires&lt;/code&gt; as an annotation hint, that the proofed condition furthermore is &lt;code&gt;true&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;So it comes to the effect, that using the following contract definition causes ReSharper to squiggle the next access and output a wrong hint:&lt;/p&gt;</description></item></channel></rss>