robert-mcginley / de4dot-installer Goto Github PK

Need to release the current Caphyon Advanced Installer 10.6 installer project file in this repo. Need to evaluate it's content to ensure no personal or identifying data is contained within it before adding it to this repo.

Separate the de4dot x86 & x64 components into individual packages.
This will allow the project to provide 32bit-only packages.

Is this even needed? Is there a demand for it?

Currently the Installer is built using Caphyon Advanced Installer 10.6. While it provides pretty dialogs and such, for the project to have a more Open Source feel I would like to migrate everything to a more barebones WiX based MSI package.

Would it be feasible or necessary to provide binaries of de4dot linked against other versions of the .NET Common Language Runtime. Currently, most de4dot components are linked against .NET 2.0 except AssemblyServer-CLR40.exe and AssemblyServer-CLR40-x64.exe which are linked against .NET 4.0

• What issues would this introduce into de4dot?
• What benefits would this gain?
• Is it even necessary?
• Is there a demand for it?

_If you're reading this, please weigh in on the above items!_

_All specifications here are subject to change at any time!_

I have begun developing a GUI interface for de4dot in C#/WPF using .NET 4.5 that relies on dnlib. This project is still a work-in-progress and has not been published to GitHub yet. I do expect the installer to include this GUI once complete though.

• _What would you like to see in a de4dot GUI?_ Please let me know!
• Currently in development, the GUI calls an external de4dot instance rather than having it compiled in to the program itself
• Relies on (the awesome) dnlib for PE image validations, .NET MetaData views and other assorted features.