dotpeek

Finding the source DLL name from Interop assembly via reflection

由 佐手、 提交于 2019-12-11 05:19:34
问题 I have an Interop DLL RCW.Xyz.dll but I can't find the corresponding DLL. Because the name doesn't follow the default naming scheme Interop.Xyz.dll my guess is that the interop assembly was simply renamed. (Even if the DLL is generated by Visual Studio with a default name, if the DLL has spaces in its name, the spaces will get lost, making it hard to find the source DLL again) How can I find out the COM DLL name behind the interop assembly? I assume I need to use disassembly tools. Preferably

DotPeek PDB generation for assemblies without debug directory

由 浪子不回头ぞ 提交于 2019-12-03 01:50:17
I'm attempting to use JetBrains dotPeek 1.4 symbol server however I've encountered some 3rd party assemblies that fail, with dotPeek status of: Pdb has not been generated because assembly does not contain debug directory Using CFF Explorer I've discovered that these assemblies have empty "Debug Directory" Portable Executable (PE) header values. Is there an (easy) way to edit the PE to add Debug Directory header values? de4dot creates invalid .net executable module in the eyes of dotPeek. It's problem of dotPeek, not de4dot, however. But since we do not have sources of dotPeek we ought to

Dotpeek recompile decompiled files

由 半城伤御伤魂 提交于 2019-12-01 08:18:44
How i can recompile my edited codes Or replace it with original files and save it as exe in dotpeek ? I try to recompile edited files and save it but i cant If you found any way please share Thanks Right click the opened file in Assembly Explorer pane and choose, Export to Project, this will save it as a Visual Studio Project that you can open and work towards compiling. 来源： https://stackoverflow.com/questions/27365003/dotpeek-recompile-decompiled-files
订阅 dotpeek