« Run multiple websites in Windows XP with IISAdmin.NET | Main | Amazon S3 Webservice: The best storage deal on the planet »

September 26, 2007


TrackBack URL for this entry:

Listed below are links to weblogs that reference Hack .NET Framework : Use private classes to fulfill your need:


Mark Brackett

What a greay way to exponetially increase your maintenance burden, get rid of static compiler checks, and ensure your code breaks fabulously on the next Framework release!
Seriously, there's a reason code is marked private or internal. It's not for public consumption, and does not constitute a part of the API. It is subject to breaking changes at Microsoft's whim, with no publishing of those changes. It has no documented (read: supported) contract, and may not be fit for your purpose.
Summary: It's a Bad Idea...

Shafqat Ahmed

Well, thats true. I am not suggesting you use this approach to write your commercial application or some framework or library. There are many small console applications one may need to write to automate some of their routine work. Sometimes you write a program that is not even reused.

Now, lets think about the fact why I want to use a private code in an assembly. Because I am writing something dispensible and don't have time to write it fully from scratch. What kind of code you don't have time to write?! The one that is dispensible. In those scenarios this could be a useful approach.


Hi, is there any add-in in reflector for editing windows dll such as mscorlib.dll?

Shafqat Ahmed

For third party dlls you can decmpile and recompile since there is a File Disassembler plugin for reflector.

But if you want to edit it then you will have to edit the IL. Try the reflexil plugin located at

But this will not work for GAC dlls becuase their content is protected from tamper.

By the way, you can also find a lot of reflector plugins here. http://www.codeplex.com/reflectoraddins

The comments to this entry are closed.