ILSpy mod by Medsft: NET assembly browser and decompiler, debugger, Hi

[killdisk]

Hello !  ILSpy and ILSpector are the best tools ever seen !! Compliments to the developer / Developers !

 

I see that it show how the item on a dialog resource are placed (coordinates and order of the buttons, textbox, and so on..).

So... would it be possible to re-create this dialog by the software ? Or just show a "visual" copy of the disposition of the buttons ?

 

I need this to understand which button correspond to which function on the .net application i am studying. I see "button_1_click" but can't understand which one is "button 1".

I hope i have explained well my question...

 

thanks !

regards

[Medsft]

How to find "button 1"

 

[skypeaful]

The link IlSpector 3.3 in homepage are corrupted. Please Medsft or someone reupload. Thanks

[MokneyDonkey]

1.- can not save the code, and

2.- if you open an assembly and select save assembly it crashes:

System.IO.__Error.WinIOError()

* Could not find a part of the path 'C:\Users\*******\Downloads\WCP_Editor-cleaned_saved_8\2\2015_1.exe'.

* DirectoryNotFoundException

2.- original file name opened: WCP_Editor-cleaned.exe

Windows 10 ent. X64

Great Program though, thank you

[Medsft]

New version 3.5.0 (A gift from Santa)

- added: rename for overrided method (context menu - rename)
- fixed: breakpoints did not work
- added: auto breakpoint for external methods (Breakpoint menu)
- added: auto breakpoint for external classes (Breakpoint menu)
- added: x86-x64 native code disasm (click on unmanaged method)
- added: options for x64-64 disasm (option im main menu)
- added: byte-patch for native methods (Edit as bytes contextmenu)(view tutorials)
- added: OllyDbg OD2Plg breakpoints export (view tutorials)
- added: size correction for native methods body
- added: x86-64 assembler support as byte-patch
- fixed: "Restore original bytes" working for both managed and native

[Medsft]

New version 3.6.0

+ add unmangle method body (wickyhu tech.)
+ add plugin`s system to deobuscate method body, based on de4dot tech (Early version)
(Source include). Add 2 plugin: C...Ex,Ne.R...r
+ add assembly comparer
+ add reference editor

+ add Contributors
- fix (show hidden name tech. IgnoreNameCollection works correctly)
- fix (show constant`s in Hex)

!!! Check Readme.txt before install

[samoray]

Thank you Medsoft for your great tool;

but honestly I cant get it to work, whenever I click a button it show : sorry, we crashed.

here is  a screen shot

[Medsft]

win8.0 64?

Include clean config file put it \Users\Admin\AppData\Roaming\ICSharpCode\

not use system path aka programdata to install AddPack,

my path (sample) 

ILSpy.NEXT.xml

[Medsft]

new version 3.6.1

-fix error "bad string in base64"

+add standalone installer

[Medsft]

new version 3.7.5

- fix option "Show hidden name" algorithm processing speed improved
- fix debugger core more stable
+ add method local`s panel (debugger)(with save value to disk)
+ add method argument`s panel (debugger)(with save value to disk)
+ add process memory panel (with dump region to disk) 
+ add module`s panel (with dump module to disk)
- fix stack panel
+ change option: view locale`s in IL as C#
+ add "Goto MDToken" to context menu
- fix: patch algorithm updated to support code block alignments with NOPs 

[Lig]

On 8/12/2016 at 11:43 AM, Medsft said:

new version 3.7.5

- fix option "Show hidden name" algorithm processing speed improved
- fix debugger core more stable
+ add method local`s panel (debugger)(with save value to disk)
+ add method argument`s panel (debugger)(with save value to disk)
+ add process memory panel (with dump region to disk) 
+ add module`s panel (with dump module to disk)
- fix stack panel
+ change option: view locale`s in IL as C#
+ add "Goto MDToken" to context menu
- fix: patch algorithm updated to support code block alignments with NOPs 

file protected with confuserex 1.0 give me error - i'm newbie with re maybe i need do something in ollydbg first idk but i want learn not only use unpackers:

[Kingmaker_oo7]

On 1/30/2015 at 7:34 PM, Medsft said:

ILSpy mod by Medsft: NET assembly browser and decompiler, debugger, High and Low level Editor

Project renamed.

ILSpy NEXT. NET assembly browser and decompiler, debugger, High and Low level Editor

Description:

ILSpy (latest ILSpy public version 2.2.0.1737)

-add debugger from the SharpDeveloper studio

-add CopyFullyQualifiedTypeName.Plugin

-add OpCodeTableForm

-add to treeview contextmenu: 

- strong name utility

- rename class utility

- Jump to EntryPoint

- string viewer utility (search enable)

- extension exeecute utility (reservation work enable)

- hexeditor methodbody utility (runtime compilation enable, 

- search any text in decompileTextView

- find method call

- Analyze. Reference calls positioning and highlight ("IL Code" view)

two technologies save the result(High Level:recompile assembly 

and Low Level:Binary Patch(See results and work in Patch_table)))

add to decompiletextview contextmenu:

- replace instruction (High Level,need recompile to save assembly)

- nop instruction (High Level,need recompile to save assembly)

- reverse branch (High Level,need recompile to save assembly)

- nop instruction (Low Level, no need recompile binary patch see Patch Table)

- reverse branch (Low Level, no need recompile binary patch see Patch Table)

- class or method injector (High level)

- "Undo" operation

Mono.Cecil

-ignore null type (Read TypeDefinition)

-ignore invalid parameter(Read MethodDefinition)

-ignore invalid generic argument()

-ignore invalid attribute (if (attribute.Constructor == null) continue;)

-ignore invalid signature(GetSecurityDeclarationSignature)

-fix handle null value in obfuscated assembly

-add ToString for CustomAttributeArgument

-add ToString for CustomAttributeNamedArgument

-ignore null element(MemberDefinition)

-avoid recursive declaringtype of some obfuscated assemblies,currently only one level checking

-add AllMemberReferences(IEnumerable<MemberReference> GetMemberReferences)

-add ElementTypeIntValue(ElementTypeIntValue)

-add support to read/write directly from bytes(FromBytes)

-Read reloc section, Contributed by Khiem Nguyen

-add alternative "Save" technology modified assembly (support obfuscated assembly)

Pack "ALL in One"

 

The latest releases of ILSpy.NEXT on http://il4re.ml//

 

[t]We are opened! Welcome, guys.[/t]

 

Last build: 12_08_2016

Sorry for my bad English and WPF

 

please reupload 

[Medsft]

I am working on site restoration

[Medsft]

h__ps://my-files.ru/wcun0h
pass: exelab

[xlfj521]

On 12/6/2019 at 5:46 PM, Medsft said:

h__ps://my-files.ru/wcun0h
pass: exelab

very good

[Medsft]

h__ps://my-files.ru/ol3d5q
pass: exelab

+ Find method by RVA

[sirp]

any news  @Medsft ?  the my-files.ru seems down

[jackyjask]

@Medsft  what happened to your home site?

Looks like it is down

 

I've uploaded latest ver 3.7.6 over here

https://mir.cr/0FPU7GYS
 

[zackmark29]

Anyone has updated download link?

[kao]

Sorry, didn't save that one.

You could use dnSpy instead, it's superior in every possible way.

[jackyjask]

On 11/9/2022 at 9:03 PM, kao said:

You could use dnSpy instead, it's superior in every possible way.

it can't debug .NET 5/6/7... sadly

 

[kao]

@jackyjask: ...and you think that this 5+ years old, unmaintained mod can?

I managed to find the installer of 3.7.6: https://mega.nz/file/N5ATzATD#bbyxqlP3LlVUa7J-9qbVm8pSiwbwV70csoJ_Mk5Moig
I still think it's a piece of junk. But if someone wants to play with it, feel free to do that.

Edited November 19, 2022 by kao

[ElektroKill]

6 hours ago, jackyjask said:

it can't debug .NET 5/6/7... sadly

 

@jackyjask Hi, if you are facing issues with dnSpy please try dnSpyEx fork. It contains quite a few bug fixes relating to various components.
Link: https://github.com/dnSpyEx/dnSpy

If the issue persists, it would be great if you could open a detailed issue report which contains the file you are trying to debug as well as specific issues you have faced and how to reproduce them.
Link to issue tracker: https://github.com/dnSpyEx/dnSpy/issues

 

[jackyjask]

@ElektroKill  does new dnSpyEx attach/debug .net 5/6/7? I've found an issue saying about some issues with it?

https://github.com/dnSpyEx/dnSpy/issues/48

[ElektroKill]

8 hours ago, jackyjask said:

@ElektroKill  does new dnSpyEx attach/debug .net 5/6/7? I've found an issue saying about some issues with it?

https://github.com/dnSpyEx/dnSpy/issues/48

Hi, the issue you found is a rare case of the debugger not working on a .net 5 bundled exe. I have not been able to reproduce it with other bundles or other files designed to run on .net 5, 6, or 7. dnSpyEx is perfectly capable to attach or start debugging a .NET Core executable other then this rare case I have not been able to trigger anywhere else.

EDIT: dnSpy can attach to any executable built using .NET Core/.NET 5,6,7 unless it’s a self contained bundled file published in release mode. If it’s your file is of such type, take a look at my latest comment in the issue you linked on how to convert a self contained application into a normal one!

 

Edited November 26, 2022 by ElektroKill
Add additional information