http://blogs.msdn.com/davbr/archive/2006/02/27/bug-inspecting-value-type-returns.aspx12/6/2007 Update: The bug described below has been fixed in CLR 2.0 SP1.&#160; (See this post for more info.)&#160; However, you may still find this info useful as a tutorial on performing IL rewriting. Holger, a helpful reader of this blog, has pointeden-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/davbr/archive/2006/02/27/bug-inspecting-value-type-returns.aspx#540487Tue, 28 Feb 2006 14:07:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:540487Jason Haleyhttp://blogs.msdn.com/davbr/archive/2006/02/27/bug-inspecting-value-type-returns.aspx#620932Wed, 07 Jun 2006 19:47:22 GMT91d46819-8472-40ad-a661-2c78acb4018c:620932David Broman's CLR Profiling API BlogPreviously, I posted about a bug with using the CLR Profiling API to inspect value-type return values....http://blogs.msdn.com/davbr/archive/2006/02/27/bug-inspecting-value-type-returns.aspx#1823931Wed, 07 Mar 2007 06:13:19 GMT91d46819-8472-40ad-a661-2c78acb4018c:1823931David Broman's CLR Profiling API Blog<p>A frequent topic of discussion between those of us on the CLR Profiling API team at Microsoft and our</p> http://blogs.msdn.com/davbr/archive/2006/02/27/bug-inspecting-value-type-returns.aspx#6682525Thu, 06 Dec 2007 20:47:42 GMT91d46819-8472-40ad-a661-2c78acb4018c:6682525David Broman's CLR Profiling API Blog<p>With the recent release of the Microsoft .NET Framework 3.5, not to mention prior versions like Microsoft</p> http://blogs.msdn.com/davbr/archive/2006/02/27/bug-inspecting-value-type-returns.aspx#6682589Thu, 06 Dec 2007 20:51:15 GMT91d46819-8472-40ad-a661-2c78acb4018c:6682589Noticias externas<p>With the recent release of the Microsoft .NET Framework 3.5, not to mention prior versions like Microsoft</p>