Essentially need to read the dependencies programmatically without loading the assembly itself, as then you can't unload them
+2
A:
Kumar,
You CAN unload .Net DLLs but you have to use the AppDomain object to load them in the first place and then again to unload.
Take a look: http://msdn.microsoft.com/en-us/library/system.appdomain(VS.80).aspx
If you still want to avoid this type of process, i suppose you could parse the the DLL yourself but that would be much more work than using the AppDomain i think.
-p
Paul Sasik
2009-07-31 14:24:18
The problem is resolving the dependencies of the dll in the new AppDomain sandboxsomehow, sandBox.AssemblyResolve += new ResolveEventHandler(reh)generates an error saying the current assembly not found ???any clues ?
Kumar
2009-07-31 17:53:00
A:
Hope you are expecting Ildasm.exe (intermediate language disassembler)
http://msdn.microsoft.com/en-us/library/aa309387(VS.71).aspx
anishmarokey
2009-07-31 14:24:34
+1
A:
2 solutions come to my mind, although I think there's easier way (which I forgot or don't know :) ):
1. Load your assemblies using some additional AppDomain that you can create. Unloading whole AddDomain will also unload loaded assemblies (but only those, which were loaded using this AppDomain).
2. Use some api, for example CCI that allows you to look inside managed dll's without loading it using reflection mechanism.
Ravadre
2009-07-31 14:26:12
looking at it and going nowhere...the only sample i found is http://www.codeproject.com/KB/recipes/Not_Used_Analysis.aspx but it's old and doesn't compile
Kumar
2009-08-03 17:21:56
i got it working with Cecil but would like to use CCI since it's used internally by MS and is likely to be more current
Kumar
2009-08-03 17:22:42
There are 3 CCI related projects on codeplex, each with it's own samples (ranges from inspecting some resources to mini compiler), they are fairly hard to understand (I think authors are aware of the fact, that they need to introduce some tutorials on this one :) ), but you could check those. Personally, I'm interested in rewriting my compiler (based on reflection) to CCI, but I'm waiting for more informations on libraries (tutorials, books?).
Ravadre
2009-08-03 17:45:40
A:
I'm sure someone will correct me if I'm wrong, but isn't the manifest just another resource in the DLL? If so, you can read it just like any other resource.
Here is an open source tool that lets you explore a DLLs resources:
http://www.wilsonc.demon.co.uk/d10resourceeditor.htm
And sure enough, I can see embedded manifests with it.
So, load the DLL using LoadLibrary() and go resource hunting.
Daniel Paull
2009-07-31 14:43:35
LoadLibrary() does not worked with managed dll's from what i seem to have read earlier
Kumar
2009-07-31 18:19:16
+1
A:
found this System.Reflection.Assembly.ReflectionOnlyLoadFrom(path) does the trick
Kumar
2009-08-04 14:20:58