http://blogs.msdn.com/thottams/archive/2007/02/01/using-ilasm-and-ildasm.aspxI wanted to write another small sample to demonstrate how you can use ilasm to modify a compiled assembly. The sample is very simple, but demonstrates the concept well. Let us take App.cs which contains the following code: using System; public class sampleenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/thottams/archive/2007/02/01/using-ilasm-and-ildasm.aspx#1577802Fri, 02 Feb 2007 03:22:21 GMT91d46819-8472-40ad-a661-2c78acb4018c:1577802Alois Kraus<p>Hi Thottam,</p> <p>I have made a simple strong naming took with this technique which works quite well:</p> <p><a rel="nofollow" target="_new" href="http://geekswithblogs.net/akraus1/archive/2007/01/23/104288.aspx">http://geekswithblogs.net/akraus1/archive/2007/01/23/104288.aspx</a></p> <p>One problem that remains is debuggability. If you do such a round trip the VS 2005 debugger is no longer able to set any breakpoints. The Ilasm /Debug option does not help much since I end up either in IL code or if I copy the original pdb at the recompiled exe location it is not loaded for some reason.</p> <p>Yours,</p> <p> &nbsp; Alois Kraus</p> http://blogs.msdn.com/thottams/archive/2007/02/01/using-ilasm-and-ildasm.aspx#1591063Sat, 03 Feb 2007 19:34:30 GMT91d46819-8472-40ad-a661-2c78acb4018c:1591063thottams@microsoft.com<p>Thanks for the feedback. I agree. The down side to this is debuggability. I have seen lots of people use this approach to achieve minor tweaks to their assemblies, if their assembly was generated by a tool. </p>