gac

There seems to be lots of different ways to register assemblies with the GAC, as in, they 'work'. However, what's the "proper" way of doing it? In response to Lou Franco (and gacutil): I'm using Gacutil for development, but it seems to me to be not the proper way to install it, since gacutil isn't included in the basic .NET utilities past .NET 1.1 - it's only a developer tool. Additional: Gacutil (as seen in responses below) is not redistributable, and therefore should not be used in any app that you intend to give to people who are not developers. AKA, customers. See This blog post (and

As I currently understand in the full .NET Framework when we install the framework to the machine it deploys the whole BCL to the computer's GAC. In that way when we develop a software with .NET and deploy to that computer it'll use the BCL assemblies which are made available in the GAC when the .NET Framework itself was installed. Now, as I know CoreFX is the equivalent of the BCL for the new .NET Core. The main difference, however, is that we can specify in the project.json exactly which pieces of the CoreFX we need. My question is: when we deploy .NET Core apps, is there any GAC equivalent

Can I configure a .NET application in a way (settings in Visual Studio) that it references a "local" assembly (not in GAC ) instead of an assembly within the GAC, although both assemblies have the same name and the same version? If both assemblies are strong-named (signed), the CLR will always load from the GAC. Here are the steps the runtime uses to resolve assembly references (from How the Runtime Locates Assemblies ): Determines the correct assembly version by examining applicable configuration files, including the application configuration file, publisher policy file, and machine

This sounds related to this question , but they aren't the same thing. That question had no assemblies showing up. Mine has everything except the specific one I installed. I'm hoping someone has a solution to this... am I doing something wrong? Or did I find some bug in VS? I am using Visual Studio 2010 Professional Beta 2 on Windows 7 Ultimate. I just downloaded Rhino Mocks and decided to install it into the GAC using the command-line utility GACUTIL. I then rebooted. Here you can see the assembly in my GAC (click to enlarge): And here is the list of assemblies available to me in Visual

I installed the VS2010 and .NET 4.0, then I compiled an assembly and ran the gacutil using the exe available on %ProgramFiles%\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools The output of the executable said the assembly was sucessfully installed on Global Assembly Cache. However, when I go to %WINDIR%\assembly folder I cannot find the assembly I installed using the .NET Framework 4.0 gacutil . I've seen some posts saying the .NET Framework 4.0 has a separated GAC, but what I haven't found was where it is located. May someone to help me to check where can I see the Global Assembly Cache of

I've trying to deploy some code to a client machine, where I don't want to install MS windows SDK tools. This means don't have access to "gacutil". I also have not created an installer for my code. It seems that these might be the only two options in .net 4.0. In the past I would simply go to start, run, type "assembly", and drag and drop my dll in. Is this no longer possible? When I try to do this I get no error message, but the dll doesn't appear in the "assembly" folder. When I use gacutil on my dev machine it works properly, but the dll still doesn't appear. TizzyFoe In .net 4.0 Microsoft

I have made a .NET .DLL file, which I want to register in the GAC . I have used this command in Windows Server 2003 Command Prompt: C:\"Path of dll"\> gacutil /i dllname.dll It says the path is not correct. Do I need to use this in a .NET cmd prompt? If it is that, I am not able to locate the .NET cmd prompt. Fredrik Mörk You can do that using the gacutil tool. In its simplest form: gacutil /i yourdll.dll You find the Visual Studio Command Prompt in the start menu under Programs -> Visual Studio -> Visual Studio Tools . You'll need: Strong name your assembly (Visual Studio, Project Properties,

When one user tries to run the application, our ClickOnce application is reporting: Unable to install or run the application. The application requires stdole Version 7.0.3300.0 in the GAC. It's interesting to note that the GAC (C:\Windows\assembly) does not have stdole installed in it. How do I get it there? We are using .NET 3.5, and it has been installed on this computer. Try going to the Publish tab in the project properties and then select the Application Files button. Then set the following properties: File Name of stdole.dll Publish status to Include Download Group to Required After that