|
|
Software Engineer - Red Gate Software
July 2009 - Posts
-
Posted Friday, July 31, 2009 6:35 PM |
Yes you can, if you use the FileGenerator add-in, which you can find at: http://www.codeplex.com/FileGenReflector You may also find Denis Bauer's FileDisassembler add-in useful: http://www.denisbauer.com/NETTools/FileDisassembler.aspx FileGenerator Read More
|
-
Posted Friday, July 31, 2009 6:16 PM |
Absolutely. Just select IL in the language dropdown on the main toolbar: Once you've done this, if you right-click on a member, or type, in the browser and click Disassemble on the context menu, .NET Reflector will show you the IL for the selected Read More
|
-
Posted Friday, July 31, 2009 5:25 PM |
The answer to this is, unfortunately, no. .NET Reflector will work with any managed assemblies from .NET 1.0 onwards, and other .NET implementations, such as Mono, but it will not support portable executables-i.e., DLLs and EXEs-containing unmanaged code, Read More
|
-
Posted Friday, July 31, 2009 4:46 PM |
Yes, to some extent. You can't customize the syntax highlighting, and so forth, as you can in Visual Studio, so at the moment it's not possible to make source code in .NET Reflector look the same as it would in Visual Studio, however you can change the Read More
|
-
Posted Thursday, July 30, 2009 7:20 PM |
No. If you're having problems with assemblies and/or PDBs being locked, the likely culprit is Visual Studio, assuming you have it open at the same time as .NET Reflector. The problem seems like it might be more prevalent with Visual Studio 2005 than Visual Read More
|
-
Posted Thursday, July 30, 2009 7:04 PM |
The answer to this is, yes, to some extent. You can choose to either see only public members and types, or everything. To change this setting, go to View > Options on the main menu bar, then click Browser in the list on the left, and then choose your Read More
|
-
Posted Thursday, July 30, 2009 6:44 PM |
As with other members, .NET Reflector does support indexers. However, if you're unfamiliar with the notation this may not be immediately obvious, because indexers are treated as properties of the form Item[<index typename>] : <return typename>. Read More
|
-
Posted Thursday, July 30, 2009 5:24 PM |
There are various reasons why .NET Reflector might fail to decompile a particular method, generate source that does not match the original source code, or generate source code that will not compile without some modifications being made. I've listed some Read More
|
-
Posted Thursday, July 30, 2009 5:00 PM |
Yes, as long as you have the XML documentation file for the assembly. If the assembly is yours, you just need to make sure you generate the XML documentation file as part of your build process. Many third party code providers will also supply an XML Read More
|
-
Posted Thursday, July 30, 2009 4:23 PM |
Open up .NET Reflector and go to View > Options on the main menu. Now click on Browser in the list on the left, and then check Automatically resolve assemblies. Click OK, and the prompt should go away. Bear in mind that if you have multiple assemblies Read More
|
-
Posted Thursday, July 30, 2009 4:18 PM |
.NET Reflector actually does support .NET 3.5 decompilation; it's just not switched on by default. To enable this support use the main menu to go to View > Options, then click Disassembler in the list on the left, then select .NET 3.5 from the Optimization Read More
|
-
Posted Thursday, July 30, 2009 4:10 PM |
Yes, absolutely. You can use one of these add-ins to extract a .NET assembly to source: http://www.denisbauer.com/NETTools/FileDisassembler.aspx http://www.codeplex.com/FileGenReflector You could even use these add-ins to convert from VB to C# or Read More
|
|
|