As long as the assembly is in the app path, it will be queried by your app,
even if it is never used. If you want to get around this, hide the assembly
and use Reflection to dynamically load it. If you want to go to the nth with
dynamic loading, you can store the assembly as code and gen it at runtime
with Reflection.Emit. The source will not show up as an unloaded assembly,
even if you smack it in the /bin folder.
---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
> Hello,
>
[quoted text clipped - 6 lines]
> refernce any types in B. Is there a way to prevent this assembly from loading
> on startup?
BrianS - 07 Jan 2005 14:55 GMT
What is the correct way to "hide" the assembly. I set the file attribute to
hidden, but It still is loading the assembly.
> As long as the assembly is in the app path, it will be queried by your app,
> even if it is never used. If you want to get around this, hide the assembly
[quoted text clipped - 22 lines]
> > refernce any types in B. Is there a way to prevent this assembly from loading
> > on startup?