The dll in question is custom, from a retail/consumer software package that was first offered for sale in 2006/2007. I am fairly confident that it was compiled with Visual Studio .NET (2003).My initial attempts to understand the dll had me test-driving various proxy dll code generators. I was able to extract the exported functions (nearly 800 of them), and the code would build. Unfortunately the retail software would reject this dll because of some mismatched signature that I was eventually able to ascertain with the corflags.exe VS utility. Eventually it became clear that my version of Visual Studio was too modern to ever match this, and after some hair-pulling I acquired VS2003. Finding that it can never install properly on modern windows, I dug Windows XP out of a closet, and I now have a VM with which to build the proxy dll... signature matches, new errors are showing.It's complaining that it can't load a type, which it names. I was under the impression that the proxy dll generator was taking care of this. Spent some time making sure it wasn't missing anything, and it doesn't appear to be.But the dll is built with CLR/.NET 1.1, which is slightly strange. So I downloaded IntelliJ's dotpeek decompiler. Sure enough, this brings up a relatively small handful of classes and structs that I haven't seen before. It even shows me the c# sharp code for this (variable names don't look like decompiled/disassembled stuff... does dotnet not strip these during compilation?).So now I have a dll that looks as if it has both cpp and cs code in it both. Is that a valid/viable dll build result? I have yet to find any instructions, tutorials, or documentation that suggests this is now possible or ever was. But quite a few microsoft.com and msdn forum links are dead, so this is difficult to research. I feel as if I must be misinterpreting what I'm seeing, and that my amateurish attempts are just confusing me.If this was ever a thing, can someone tell me what buzzwords it was called by? My Microsoft jargon is pretty limited, and I'm finding a whole bunch of nothing.
Am I seeing this dll's innards correctly?
windows;decompilation;dll;.net;c#