Question

Closed. This question is seeking recommendations for books, tools, software libraries, and more. It does not meet Stack Overflow guidelines. It is not currently accepting answers.

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 7 years ago.

Improve this question

Long story short, VSS decided I wasn t allowed to have some code changes. I am missing a decent sized feature that I don t want to have to re-write (gave to a co-op as work this past summer). It works great and does what the client wants. However... I don t have the machine and the machine it was developed on has since been paved low!

Do h!

We published the site into a test environment straight from visual studio and then we copied the files into production. So I have the "compiled" files from the VS publish.

How can I go about getting that back into code? I am sure I can figure out which DLL it is in and I would assume that something like reflector is going to be my best bet? Are the original variable names retained?

Answer 1

I would use .NET reflector. Your original variable names will be preserved (providing you did not run any kind of obfuscator) if you have the PDB files as well as the DLLs.

Answer 2

I would suggest trying to reflect your compiled code and see how readable it comes out.

http://www.red-gate.com/products/reflector/

Answer 3

Reflector all the way. You can t rely on local variable names since they don t really exist (only fields retain their names), but having the matching pdb would go a long way to helping. If you use the pro/EAP version of reflector it will do must of the work for you (generating the full C# disassembly etc, so you don t have to go method-by-method or use a plugin).

You may still need to look at each directory separately, of course.

Answer 4

Best you are going to get is with a decompiler like this http://www.red-gate.com/products/reflector/. You are going to lose variable names and comments, but what you get will compile.

Sucks, but probably a lot better then starting from scratch.

Answer 5

I used Telerik s JustDecompile to get the source code back from a precompiled site. It s free and has done everything I ve needed.

http://www.telerik.com/products/decompiler.aspx

Answer 6

Salamander - a .NET decompiler http://www.remotesoft.com/salamander/index.html

I ve never used this tool, but they talked about it on .NET rocks! a while back. http://www.dotnetrocks.com/default.aspx?showNum=194

Answer 7

I had the similar issue and used Reflector to Decompile it. I got the source code, then changed the bit I wanted, and rebuild it. Then I copied that dll again to Production site. It started to reflect my changes. It was very easy and not at all difficult, maybe because Precompiled site had dlls for every page, and was updatable , so had only code-behind file in dll.

For reference: http://www.reflector.net/

友情链接