.NET decompilers
-
I wanted to share two important news with you. A new (and free) C# decompiler has been made available by Lutz Roeder. Reflector[^] was in the past "only" showing IL(L) code. Now Reflector embeds a C# decompiler plugin and it comes just as the definitive tool to unmasquerade all those CLR secrets... Reflector comes even handier than predicted with the use of hyperlinks to navigate through methods within the source code. Amazing! Anakrino[^] 1.1 has been updated. In fact, only the xml configuration file needs an update. Get it here[^]. Replace the xml file in your Anakrino install folder with this one. Caution : this xml file references paths of the form C:\WINDOWS\... and, as a consequence, you are very likely to have to replace those occurences with C:\WINNT\... Otherwise, Anakrino raises an exception when it starts. With these tools in hands, it is possible to know how EVERY .NET class is actually implemented. For native calls, just give a look at rotor.
-
I wanted to share two important news with you. A new (and free) C# decompiler has been made available by Lutz Roeder. Reflector[^] was in the past "only" showing IL(L) code. Now Reflector embeds a C# decompiler plugin and it comes just as the definitive tool to unmasquerade all those CLR secrets... Reflector comes even handier than predicted with the use of hyperlinks to navigate through methods within the source code. Amazing! Anakrino[^] 1.1 has been updated. In fact, only the xml configuration file needs an update. Get it here[^]. Replace the xml file in your Anakrino install folder with this one. Caution : this xml file references paths of the form C:\WINDOWS\... and, as a consequence, you are very likely to have to replace those occurences with C:\WINNT\... Otherwise, Anakrino raises an exception when it starts. With these tools in hands, it is possible to know how EVERY .NET class is actually implemented. For native calls, just give a look at rotor.
Stephane Rodriguez. wrote: Reflector comes even handier than predicted with the use of hyperlinks to navigate through methods within the source code. Amazing! Well, if you have a class highlighted in the TreeView, you can hit enter and it'll jump to its base type. Or if you have a method selected, hit enter and it'll jumpt to its return type. And the links were there in the IL as well. :) Stephane Rodriguez. wrote: With these tools in hands, it is possible to know how EVERY .NET class is actually implemented. For native calls, just give a look at rotor. I've been looking at Rotor. It's fairly interesting. I've been contemplating installing it so I can program against it. Maybe I'll even install Mono. :-D
Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing
-
Stephane Rodriguez. wrote: Reflector comes even handier than predicted with the use of hyperlinks to navigate through methods within the source code. Amazing! Well, if you have a class highlighted in the TreeView, you can hit enter and it'll jump to its base type. Or if you have a method selected, hit enter and it'll jumpt to its return type. And the links were there in the IL as well. :) Stephane Rodriguez. wrote: With these tools in hands, it is possible to know how EVERY .NET class is actually implemented. For native calls, just give a look at rotor. I've been looking at Rotor. It's fairly interesting. I've been contemplating installing it so I can program against it. Maybe I'll even install Mono. :-D
Hawaian shirts and shorts work too in Summer. People assume you're either a complete nut (in which case not a worthy target) or so damn good you don't need to worry about camouflage... -Anna-Jayne Metcalfe on Paintballing
-
I wanted to share two important news with you. A new (and free) C# decompiler has been made available by Lutz Roeder. Reflector[^] was in the past "only" showing IL(L) code. Now Reflector embeds a C# decompiler plugin and it comes just as the definitive tool to unmasquerade all those CLR secrets... Reflector comes even handier than predicted with the use of hyperlinks to navigate through methods within the source code. Amazing! Anakrino[^] 1.1 has been updated. In fact, only the xml configuration file needs an update. Get it here[^]. Replace the xml file in your Anakrino install folder with this one. Caution : this xml file references paths of the form C:\WINDOWS\... and, as a consequence, you are very likely to have to replace those occurences with C:\WINNT\... Otherwise, Anakrino raises an exception when it starts. With these tools in hands, it is possible to know how EVERY .NET class is actually implemented. For native calls, just give a look at rotor.
Stephane Rodriguez. wrote: has been made available by Lutz Roeder He's done some really interesting things. Thanks for the FYI. Stephane Rodriguez. wrote: With these tools in hands, it is possible to know how EVERY .NET class is actually implemented. So will you be rewriting everything, just for fun? -Nick Parker
-
Stephane Rodriguez. wrote: has been made available by Lutz Roeder He's done some really interesting things. Thanks for the FYI. Stephane Rodriguez. wrote: With these tools in hands, it is possible to know how EVERY .NET class is actually implemented. So will you be rewriting everything, just for fun? -Nick Parker
When you see the immediate benefits of these tools for those wildly posting issues, it's too bad we don't clearly show permanent links to these tools in the forum. Quite cheap an improvement. Nick Parker wrote: So will you be rewriting everything, just for fun? I don't think so. I am even thinking about giving up the interop stuff altogether, and go to a more creative side (ASP.NET). So, may be bye bye C# forum and good morning ASP.NET forum! ;) All those interop details are much like learning by heart tons and tons of tiny details. We developers were sold seamless interop, and the truth is that, just to give a crude example of where we developers are now, the CLR 1.1 does not even release running COM instances when told to (chris brumme blog). Someone bold enough could rewrite the entire Windows Forms code, or sell a total replacement. It's clearly lagging behind today's needs, especially when you see how people are used to MFC controls and the like. After all, that's business opportunities for companies like Infragistics. According to me, this portion of the run-time is utter crap (internal classes, too tightly coupled with WIN32 controls, while being hardcoded at the same time).
-
When you see the immediate benefits of these tools for those wildly posting issues, it's too bad we don't clearly show permanent links to these tools in the forum. Quite cheap an improvement. Nick Parker wrote: So will you be rewriting everything, just for fun? I don't think so. I am even thinking about giving up the interop stuff altogether, and go to a more creative side (ASP.NET). So, may be bye bye C# forum and good morning ASP.NET forum! ;) All those interop details are much like learning by heart tons and tons of tiny details. We developers were sold seamless interop, and the truth is that, just to give a crude example of where we developers are now, the CLR 1.1 does not even release running COM instances when told to (chris brumme blog). Someone bold enough could rewrite the entire Windows Forms code, or sell a total replacement. It's clearly lagging behind today's needs, especially when you see how people are used to MFC controls and the like. After all, that's business opportunities for companies like Infragistics. According to me, this portion of the run-time is utter crap (internal classes, too tightly coupled with WIN32 controls, while being hardcoded at the same time).
Stephane Rodriguez. wrote: When you see the immediate benefits of these tools for those wildly posting issues, it's too bad we don't clearly show permanent links to these tools in the forum. Quite cheap an improvement. Interesting thought, maybe you should suggest this to Chris in the Suggestions forum.... Stephane Rodriguez. wrote: So, may be bye bye C# forum and good morning ASP.NET forum! Not sure how much of a UI designer you are for Win32, however if you haven't done much web stuff you will soon hate the limitations. -Nick Parker