ildasm

问题 I'm trying to run ildasm (Intermediate Language Disassembler) installed as part of Visual Studio 2019 against .NetCore3.1 console app. Use Developer command prompt of Visual Studio 2019 and run following command ildasm.exe D:\DotNet\IntroductionToCsharp\IntroductionToCsharp\bin\Debug\netcoreapp3.1\IntroductionToCsharp\bin\Debug\netcoreapp3.1\IntroductionToCsharp.exe But following error occur: 'D:\DotNet\IntroductionToCsharp\IntroductionToCsharp\bin\Debug\netcoreapp3.1\ IntroductionToCsharp

问题 I'm trying to run ildasm (Intermediate Language Disassembler) installed as part of Visual Studio 2019 against .NetCore3.1 console app. Use Developer command prompt of Visual Studio 2019 and run following command ildasm.exe D:\DotNet\IntroductionToCsharp\IntroductionToCsharp\bin\Debug\netcoreapp3.1\IntroductionToCsharp\bin\Debug\netcoreapp3.1\IntroductionToCsharp.exe But following error occur: 'D:\DotNet\IntroductionToCsharp\IntroductionToCsharp\bin\Debug\netcoreapp3.1\ IntroductionToCsharp

问题 Is there a way to programmatically get the FileInfo/Path of the ildasm.exe/ilasm.exe executables? I'm attempting to decompile and recompile a dll/exe file appropriately after making some alterations to it (I'm guessing PostSharp does something similar to alter the IL after the compilation). I found a blog post that pointed to: var pfDir = Environment.GetFolderPath(Environment.SpecialFolders.ProgramFiles)); var sdkDir = Path.Combine(pfDir, @"Microsoft SDKs\Windows\v6.0A\bin"); ... However,

问题 In C# I can get Visual Studio to keep the delegate's argument names. For example if I have: public delegate void Blah(object myArg); public event Blah Foo; Then when I add a method to the event, Visual Studio UI automatically keeps the names and creates the method: void Form1_Foo(object myArg); But, if I declare a delegate in C++/CLI: public: delegate void Blah(Object^ myArg); event Blah^ Foo; it doesn't keep the names and creates a method with nonsense names: void Form1_Foo(object A_0) How

问题 I've a directory with a large number of dlls . I need to find all those that reference a specific dll . I'm thinking about the following solution : Loop the assemblies and invoke each one with ildasm Dump the manifest into a text file Search the text files for the required assembly name. Yet this solution feels immensely wrong to me. Is there a better way to achieve it? 回答1: You could write a small tool for that purpose, using Reflection to find the referenced assemblies: string[] fileNames =

问题 I have several Unmanaged C++ written lib files which I need to link to Managed C++ dll. Then I need to invoke functions of this Managed C++ from C# application. First step is OK - Managed C++ dll is created, I can see with ildasm that it exports functions I need. However when I try to call this function from my C#-written test app it says: An unhandled exception of type 'System.IO.FileLoadException' occurred in Unknown Module. A procedure imported by {MyManagedCPP.dll} could not be loaded.

问题 I'm having a hard time trying to (Dis)assemble a dll using the Visual Studio command prompt, don't look that simple as I see in the microsoft page. I'm using the ildasm for these way: ildasm myLibrary.dll output:MyLibrary.il And I get: Unable to open 'MyLibrary.il' for output. I also tried the full path: ildasm directory\myLibrary.dll output:directory\MyLibrary.il And I get: MULTIPLE INPUT FILES SPECIFIED Using the ildasm GUI actually works, but when I use the ilasm: ilasm myLibrary.il /dll I

问题 when my .net exe runs, it loads the correct .net assemblies at rumtime. i understand that there is a probing process that happens. my question is that if i open up the .net exe/dll in ildasm, i only the .extern reference to the mscorlib.dll, not others. so how does clr gets the information required for doing the probing of the .net referenced assemlies? i have an example project and the images here. so in this case, i dont see the .net assembly references anywhere like System, System.Xml.Linq

问题 Is there a better way to modify the version information of a .NET assembly of the one I am currently using. My current approach is the following. I do disassemble the assembly with ildasm : ildasm /nobar Riolo.WebUI.dll /out=Riolo.WebUI.il This will generated also a Riolo.WebUI.res compiled resource file, that I then open and modify with the user interface of Visual Studio, then I do reassemble the assembly back with ilasm : ilasm Riolo.WebUI.il /OUTPUT=Riolo.WebUI.dll /RESOURCE=Riolo.WebUI

问题 I am trying to produce a tool which is smart enough to programmtically examine release version binaries produced by identical C# code compiled on two seperate machinces at different times and conclude that the code was identical while being able to pick up any code changes if present in the c# code used to produce these binaries. I have tried using a number of approaches but in order to keep this short i'll just stick to the latest attempt. I run ildasm with the /text option on the binaries