Re: GAC Information
From: Richard Blewett [DevelopMentor] (richardb_at_develop.com)
Date: 10/13/04
- Next message: Jon Davis: "Re: The Variant is back!!"
- Previous message: Pam Ammond: "DataBind()"
- In reply to: John Lee: "Re: GAC Information"
- Next in thread: John Lee: "Re: GAC Information"
- Reply: John Lee: "Re: GAC Information"
- Messages sorted by: [ date ] [ thread ]
To: microsoft.public.dotnet.languages.csharp Date: Wed, 13 Oct 2004 05:18:53 -0700
If you look in the same physical directory as the assembly (c:\windows\assembly\GAC\xxxx) there you will see a file called __assemblyinfo__.ini. If you take a look in this file (its in ini file format unsurprisingly) you will see a URL value which is the directory from which the assembly was GAC'd
(I'll have a think about the Biztalk side of things)
Regards
Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog
nntp://news.microsoft.com/microsoft.public.dotnet.languages.csharp/ Hi, Phil,
Try to right click "System.Messaging 1.0.5000.0" and the codebase should be
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/System.Messaging.dll
or try to use GACUTIL to gac one of your own strong named dll and then right
click that assembly there you should be able to see the codebase.
My question is how/where does the shfusion gets that information? It must be
stored somewhere because when you GAC an assembly using gacutil you passed
the assembly path and that path will be shown as codebase. How can I
programatically get it? - GAC viewer can get that info so it should be
available somewhere.
Relevant Pages
... If you need to mimic the process of 'gacutil' and/or 'regasm' because ... p.GacInstall(file); // for gac installation ... > codebase on the dll's properties. ...
(microsoft.public.dotnet.general)
... look at properties, the is an entry for Codebase, which references the ... location of the dll I installed using the GACUTIL. ... If I check the GAC after I use the installer there is no entry for the ... codebase on the dll's properties. ...
(microsoft.public.dotnet.general)
... Thanks for your posting. ... GAC ... CODEBASE setting (in config file) ... So the codebase setting is the one you can make use of, ...
(microsoft.public.dotnet.framework)
... Try to right click "System.Messaging 1.0.5000.0" and the codebase should be ... or try to use GACUTIL to gac one of your own strong named dll and then right ... Or anyone know a better solution for my real problem: I have a dll that will ... >> shown as codebase when you use the Windows explorer to browse ...
(microsoft.public.dotnet.languages.csharp)
... > If you look in the same physical directory as the assembly ... > click that assembly there you should be able to see the codebase. ... > stored somewhere because when you GAC an assembly using gacutil you passed ... > the assembly path and that path will be shown as codebase. ...
(microsoft.public.dotnet.languages.csharp)