looks like we have a fix in Release 1.4.40602.0 (June 2, 2011)
http://research.microsoft.com/en-us/projects/contracts/releasenotes.aspx

will verify ASAP and post results

-- 
--
mono-cecil

Reply via email to