IL editor

  • Thread starter Thread starter Chris
  • Start date Start date
hi Chris
You can find the IL disassempler .open the command Prompt of Visual studio
. type ILdasm. the tool is opened. You can then open any PE exe and view
its IL, dump the content to text file among some other options
Mohamed Mahfouz
MEA Developer Support Center
ITworx on behalf of Microsoft EMEA GTSC
 
anything can be an il editor... you probably mean disassembler or
decompiler? do a google for "reflector".
 
....the first programming environment for the Microsoft Intermediate Language
(MSIL) in which the .NET Framework is based. With this program, you will be
able to decompile executables and libraries based on the Microsoft .NET
Framework to see how they work or write your own ones in the most optimized
language for this platform.

http://ilide.europe.webmatrixhosting.net/


--
FF
www.francofigun.com.ar
www.microsofties.com.ar
UIN: 305336919
MSN: (e-mail address removed)
 
Chris said:
Hi,

does anybody know where I can find an IL-editor ?

thnx

Chris
Click to expand...
Chris,
have a look at LSW DotNet-Lab ( www.lesser-software.com/lswdnl.htm ).
It comes with an MSIL-Editor you can edit MSIL on a binary level ( e.g
deleting statements from methods / deleting methods from classes ).
We have added Graphical MSIL - see an example.
http://www.lesser-software.com/images/Screenshots/LSW_DotNet_Tools/LSW-DNRB/
1.3/HTML-VML/SeparationSample.html

LSW DotNet-Lab is not released yet - there exist an old Prerelease dated
06/16/2003. The new version is based on a new Smalltalk Virtual-Machine & a
new GUI Library
we hop to release it very soon.

regards, Frank
 
I'm using ILDASM + my favourite text editor + color coding.

I've also seen a free VS add-in for IL at GotDotNet Workspaces.

Frank, your screenshot is nice but so far your app has been crashing on any
machine I tested it with. Worse, I cant uninstall it either. Furthermore,
the "we will ship these features anytime soon" messages you are posting for
almost a year now are quite annoying. Why do you need a team of people to
write your own runtime and language to finally come up with a commercial
clone of .NET Reflector?
 
Jason,

you are right, we are behind our schedule.
I am sorry for that trouble with the uninstall. Just delete the exe and the
shortcuts manually - there is nothing left on your computer - we will
document it.
There is a problem in RC6 with LSWDNRB.ini and assemblyCachesRootDir - just
edit it manually and point it to a valid location.

No our tool is **not** a clone of the reflector - it has very different
features.
Also decompiling is something which can have very different quality - we
focus to have the best which takes time.

But the real delays where the necessary decision to extend our Smalltalk VM
for preparation to Longhorn , to use our new Unicode GUI fraework etc.
The important thing is because we are running outside the CLR we have
distinguished features ( we can load/unload assemblies without having them
locked ).
We don't need a specific exe for different framework versions etc.
Finally we will publish a very exciting tool has a lot of features ( UML
Diagrams / Obfuscator / Binary Assembly editor ) is extended continuosly
and will work accross all .Net Frameworks. Also it will work under Linux.

Our Smalltalk VM allows us to create tools where ** Debug and continue ** is
a natural feature / Classes can be changed without loosing instances of the
class etc.

regards, Frank
 
I have to agree with Jason. It is a clone. Given that your tool is
infinitely more expensive you should have better arguments than what you
mentioned below. Take a look at Reflector 4.0 which is available at
http://aisto.com/roeder/dotnet. It loads and unloads assemblies, works with
different framework versions (including Whidbey) and I have no idea what you
mean with "different quality" of the decompiler.

Frank Lesser said:
Jason,

you are right, we are behind our schedule.
I am sorry for that trouble with the uninstall. Just delete the exe and the
shortcuts manually - there is nothing left on your computer - we will
document it.
There is a problem in RC6 with LSWDNRB.ini and assemblyCachesRootDir - just
edit it manually and point it to a valid location.

No our tool is **not** a clone of the reflector - it has very different
features.
Also decompiling is something which can have very different quality - we
focus to have the best which takes time.

But the real delays where the necessary decision to extend our Smalltalk VM
for preparation to Longhorn , to use our new Unicode GUI fraework etc.
The important thing is because we are running outside the CLR we have
distinguished features ( we can load/unload assemblies without having them
locked ).
We don't need a specific exe for different framework versions etc.
Finally we will publish a very exciting tool has a lot of features ( UML
Diagrams / Obfuscator / Binary Assembly editor ) is extended continuosly
and will work accross all .Net Frameworks. Also it will work under Linux.

Our Smalltalk VM allows us to create tools where ** Debug and continue ** is
a natural feature / Classes can be changed without loosing instances of the
class etc.

regards, Frank




Jason Sagar said:
I'm using ILDASM + my favourite text editor + color coding.

I've also seen a free VS add-in for IL at GotDotNet Workspaces.

Frank, your screenshot is nice but so far your app has been crashing on any
machine I tested it with. Worse, I cant uninstall it either. Furthermore,
the "we will ship these features anytime soon" messages you are posting for
almost a year now are quite annoying. Why do you need a team of people to
write your own runtime and language to finally come up with a commercial
clone of .NET Reflector?
Click to expand...
http://www.lesser-software.com/images/Screenshots/LSW_DotNet_Tools/LSW-DNRB/ Virtual-Machine
&
Click to expand...
Click to expand...
 
Chris,
Better discuss further if we have published - will be very soon. BTW we are
finnishing decompilation of Managed C++, obfuscator & binary assembly editor
are included
And decompilation quality means that we are able to decompile almost all
code which contain complex control structures.
The GUI is multiwindow with a lot of different viewmodes.
We have also UML Diagrams & Visual Syntax for C# / MSIL
we are working on a script language which allows you to exeecute code direct
in a Workspace.
decompilation of unmanaged code ( www.lesser-software.com/lswbl.htm ) will
also be included in a later version.

Frank
 
My point is that your app is cloning Reflector, you're saying you have a
clone with some additional features ready soon. Have you thought about
adding UML stuff as Reflector add-in? The obfuscator should be a standalone
tool anyway and there are lots of them. Also, I wonder why you're writing
your own script language. Why not have a managed C# API?

Beyond that, good luck with your release.
 
Hi Chris,

I don't like the word clone because it doesn't reflect what we are doing.
Smalltalk book from the mid 70ies ( Smalltalk 72 ) does contain a System
Browser - so we can say the Relector is a clone of these Smalltalk -
Browsers
And we didn't even look at Reflector if we created our Browser. We tried to
"clone" the Smalltalk-Browser for .NET
And I think Reflector and our Browser are very different in the GUI
philosophy.

Our concept is very different from Reflector - we have build everything on
top of our Smalltalk - and we are very happy with it.
The UML stuff is based on a huge Graph-Rendering Library which would be very
difficult to port from Smalltalk to C#. And why we should enhance the
Reflector.
We are very busy to enhance our own Browser.
 
Chris,,
I hit the Return key to earaly - anyway returning to the work - will see if
we have published the browser...
regards , Frank
 
Back
Top