gac

问题 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 \'gacutil\' is not recognized as an internal or external command, operable program or batch file. 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. 回答1: You can do that using the gacutil tool. In its simplest form: gacutil /i yourdll

问题 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. 回答1: Try going to the Publish tab in the project properties and then select the Application Files button. Then set

问题 Just looking for a short overview of GAC for a layman, not a link please. 回答1: Right, so basically it's a way to keep DLLs globally accessible without worrying about conflicts. No more DLL Hell. Each architecture and version gets it's own place to live. It also gets it own way to browse it in Explorer, so if you go to C:\Windows\assembly In windows explorer it lists all the DLLs. But if you fire up cmd , you can see how it's really structured: C:\Users\tritter>cd C:\Windows\assembly C:

问题 I have a .NET assembly that (for reasons outside my control) must be in the GAC. However, the same assembly is used by another program, which has a its own copy of an older version of the same assembly. It must use its own copy and not whatever is in the GAC. Proper versioning is probably more hassle than it\'s worth in this case, for reasons I won\'t go into. My questions is: is there anyway to tell .NET: just use THIS DLL, right here in this directory - ignore whatever you find in the GAC

问题 I am trying to use ViewBag in my application, I have all of the recent dlls, the latest version of MVC 3, but yet I am still getting the Error: \"The name \'ViewBag\' does not exist in the current context\" I have even uninstalled and then re-installed MVC 3 and yet there is no change. Also, I do not believe that the dll\'s are showing up in the GAC. What might be my problem? Or how to add the dll\'s to the GAC? 回答1: You need to add the MVC-specific Razor configuration to your web.config. See

问题 And on top of that, are there cases where one has to use the global assembly cache or where one cannot use it? 回答1: Loading assemblies from GAC mean less overhead and security that your application will always load correct version of .NET library You shouldn't ngen assemblies that are outside of GAC, because there will be almost no performance gain, in many cases even loss in performance. You're already using GAC, because all standard .NET assemblies are actually in GAC and ngened (during

问题 I would like to know practically what kind of Assemblies should I deploy in GAC. Case 1 : If in my Solution multiple project uses log4net.dll then should it be deployed in GAC? Case 2 : If I have multiple application deployed in a machine each using log4net.dll is this the reason enough to deploy log4net.dll into GAC? 回答1: Question: When should I deploy my assemblies into the GAC? Answer: Never Actual, honest, Real Answer: Hardly Ever Discussion Only drop things into the GAC when multiple

问题 %windir%\\Microsoft.NET\\assembly\\ is the new GAC. Does it mean now we have to manage two GACs, one for .NET 2.0-3.5 applications and the other for .NET 4.0 applications? The question is, why? 回答1: Yes since there are 2 distinct Global Assembly Cache (GAC), you will have to manage each of them individually. In .NET Framework 4.0, the GAC went through a few changes. The GAC was split into two, one for each CLR. The CLR version used for both .NET Framework 2.0 and .NET Framework 3.5 is CLR 2.0