Re: strong name woes

From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 05/28/04


Date: Fri, 28 May 2004 09:31:41 -0700

Ah, that requires a registry tweak.

You need create a registry key here:
HKLM\Software\Microsoft\.NETFramework\AssemblyFolders
witht the name of your application or assembly and make sure the default
value is the path that your assemblies are actually physically installed in.
I generally use Windows Installer to do this for me when it installs
something in the GAC. You can do this very easily from Visual Studio.

Joe K.

"ari" <anonymous@discussions.microsoft.com> wrote in message
news:C1A91E52-C3EA-4E58-9774-EDC02424C212@microsoft.com...
> I thought once you get your .dll in the gac it will show up when you
select add/remove items... on the Visual Studio Toolbar. If not, how do I
get my custom control to show up in the .Net Components tab of the toolbar?
> thanks in advance,
> ari



Relevant Pages

  • RE: installer woes (MSI generated by VS.NET 2003)
    ... an upgrade executes previous custom actions. ... >addition, during installation, Setup creates registry subkeys, sets ... >have custom actions for Setup that are run within the Installer class. ... >assemblies within that, but it threw a deserialization exception. ...
    (microsoft.public.vsnet.general)
  • installer woes (MSI generated by VS.NET 2003)
    ... have custom actions for Setup that are run within the Installer class. ... The Uninstall custom action in the Installer class isn't always called. ... assemblies within that, but it threw a deserialization exception. ...
    (microsoft.public.vsnet.general)
  • installer woes (MSI generated by VS.NET 2003)
    ... have custom actions for Setup that are run within the Installer class. ... The Uninstall custom action in the Installer class isn't always called. ... assemblies within that, but it threw a deserialization exception. ...
    (microsoft.public.dotnet.general)
  • Re: Using installer classes
    ... I don't believe that the Crystal reports assemblies are in the GAC on every ... to be CR because your Installer class code probably isn't referencing the CR ... What dependencies does your exe need in the Installer class code and are ...
    (microsoft.public.dotnet.framework)
  • Re: Goodbye and Best Wishes
    ... > He he, interestingly enough, that URL explicits my point. ... framework, I can, if I'm careful, make the assembly also work with the ... Installer happen only once, and unsurprisingly so, at ... versions of individual assemblies found on a machine. ...
    (borland.public.delphi.non-technical)