| Author | Message | Time |
|---|---|---|
| Imperceptus | Anyone remember how to dump the calls from a dll using link.exe? i forgot the syntax and where i wrote down the syntax. thought it was link.exe /dump -exports filename not getting what i wanted. | May 26, 2006, 11:21 PM |
| Imperceptus | dumpbin filename /exports ? im starting to think the dll im trying to ind info on doesnt have any exports. | May 27, 2006, 12:28 AM |
| Topaz | [quote author=Imperceptus link=topic=15063.msg153219#msg153219 date=1148689710] dumpbin filename /exports ? im starting to think the dll im trying to ind info on doesnt have any exports. [/quote] Tried that one, it works. | May 27, 2006, 12:54 AM |
| Imperceptus | what Can I do to try to find out the calls of an dll that has no exports? i have the source but its all in c-sharp and beyond which I dont know how to make the calls to it correctly? | May 27, 2006, 1:06 AM |
| K | .NET DLLs are not regular DLLs. They don't import or export functions. You specify them as a reference when compiling a .NET project and the public classes are then visible. [code] csc mycode_that_uses_foo.cs /r:Foo.dll [/code] You can use reflector to view the classes and objects inside of it with Reflector for .NET, but since you already have the source, why not just look at that? | May 27, 2006, 1:35 AM |
| Myndfyr | If you're using a COM-aware C# DLL (such as MBNCSUtil), you can select Project->Add Reference to add a reference to the type library (e.g., mbncsutil.tlb). Your VB project would require you to have the .NET Framework installed on the target machine, and you'd need to have registered the C# DLL using regasm.exe or a similar utility. The DLL can be in the local folder in the global assembly cache (%windir%\Assembly) after it's been registered to be used. | May 27, 2006, 8:44 PM |
| dRAgoN | [quote author=MyndFyre[vL] link=topic=15063.msg153267#msg153267 date=1148762659] If you're using a COM-aware C# DLL (such as MBNCSUtil), you can select Project->Add Reference to add a reference to the type library (e.g., mbncsutil.tlb). Your VB project would require you to have the .NET Framework installed on the target machine, and you'd need to have registered the C# DLL using regasm.exe or a similar utility. The DLL can be in the local folder in the global assembly cache (%windir%\Assembly) after it's been registered to be used. [/quote] Or you have the creator make an installer so you dont have to fart around with crap like that. | May 27, 2006, 8:51 PM |