|
I have an old VB.NET executable for a project done some time ago. I can load it in Reflector, see the code, etc. This project does have two Windows forms in it which contains images, controls, etc. How do I regenerate this executable with a few changes to code? I.e: the client wants a few revisions and enhancements BUT can no longer find the original source code... Any help would be much appreciated |
|
In the standalone version of Reflector, you can use the "export assembly source code" context menu item to generate a project file and code for an assembly. You may then need to fix the project up a little by hand to get it compiling. |
|
Clive, I've exported assembly source code BUT did not get anything reasonable for the forms in the original executable. Do I have to manally recreate all the forms to match the code? No. The forms will be there but will not be split into the usual two files - one for user code and one for the designer generated code. The InitializeComponent will be in the same file as the type. In VS, if you double click the file, the system notices that you have a Form definition and will show it in the designer. However, the code in the initialize is serialized using the CodeDom which expects a very fixed syntax for some of the items - you may need to do some fixup by hand to get it to load.
(Feb 03 at 11:11)
Clive ♦♦
|
I should add I am running Visual Studio 2010 and running Reflector from inside VS.