In the GAC?
If I create an interop wrapper for a COM DLL and place it in the GAC, and then I reference the interop in a client app, the path shown in the Properties window shows that it comes from the GAC. However, if I reference a .NET DLL that is also registered in the GAC, the path is the same as the one I referenced (i.e., a local copy of the DLL). I realize that at runtime, the component from the GAC will be used.
My question is, is there anyway to know that DLLs that I have references to are coming from the GAC? This could be confusing for the dev/tester/cm teams.
todd
[588 byte] By [
turczytj] at [2007-12-25]
When you reference a .NET DLL that is in the GAC, set copy local to false. This will prevent the DLL being copied to your bin folder and ensure that the assembly is loaded from the GAC. You shouldnt deploy any assemblies to the folder of your application if they are being called from the GAC. Deploy those assemblies to the GAC only.
Yes, I understand how/when/where .NET DLLs get instantiated at runtime. My question is, is there a way to tell at design time that a .NET DLL I have referenced is located in the GAC? For a COM DLL, the path found in the Properties window shows the associated interop file is found in the GAC - this does not appear to be true for .NET DLLs.
