<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Don't rewrite opcodes in managed code.</title><link>http://blogs.msdn.com/b/jmstall/archive/2005/12/13/dont-rewrite-opcodes.aspx</link><description>Some tools work by replacing instructions in the target app. The tool may introduce a jump to some stub that will still execute the original instructions. This may work fine in native code, but you can't safely changed arbitrary instructions in JITed</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Don't rewrite opcodes in managed code.</title><link>http://blogs.msdn.com/b/jmstall/archive/2005/12/13/dont-rewrite-opcodes.aspx#503506</link><pubDate>Wed, 14 Dec 2005 13:19:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:503506</guid><dc:creator>David Elkind</dc:creator><description>Agree absolutely. However, we at Identify do many tricks in order to enable our code modification-based instrumentation work flawlessly in the managed code... Sometimes we are having a hard time, though... :)&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=503506" width="1" height="1"&gt;</description></item></channel></rss>