Global Assembly Cache Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of unable to install or run the application. the application requires that assembly gac this site About Us Learn more about Stack Overflow the company Business Learn unable to install or run the application. the application requires that assembly crystaldecisions more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question unable to install or run the application. the application requires version 4.0 full x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up
Unable To Install Or Run The Application The Application Requires That Assembly Microsoft Mshtml
Unable to install or run the application: Click Once up vote 16 down vote favorite 1 I published my .net application using ClickOnce, and all my users get the following error message on trying to open the program: "Unable to install or run the application. The application requires that assembly Telerik.Windows.Data Version 2012.1.215.40 be installed in the Global Assembly Cache (GAC) first". The the application requires that assembly mysql.data be installed in the global assembly cache version I actually use in my application is NEWER than the one mentioned in the error message. I also don't have this problem on my machine which I use to develop the application. I wonder why it is looking for the older version of the dll. I can't find where it is referenced by my application. Could you please help me on this? Thanks. .net clickonce share|improve this question asked Jul 16 '12 at 13:35 David Shochet 1,23251746 1 Do you include the assembly with your application, or should it be installed from a Telerik installation application? ClickOnce applications cannot install dlls in the GAC. Instead, they must be put there by another installer application. –RLH Jul 16 '12 at 14:51 In Properties, the Publish tab, under Application Files list, I have it present as Include(Auto). In fact, I don't even need that dll. I excluded it from the project, and yet I have the same problem. Don't you know why ClickOnce (or the installation package it creates) wants that obsolete dll? –David Shochet Jul 16 '12 at 15:14 1 No, it shouldn't look
error while compiling my first C# production application. I had to do the following in Visual Studio for the project: In Solution Explorer, expand the References the application requires that assembly stdole version 7.0 be installed node and click the assembly listed in the error. Ensure Copy Local in
Unable To Install Or Run The Application. The Application Requires That Assembly Windowsbase Version
the Properties grid is set to ‘True'. In the properties of the project, Publish | Application Files Tab, ensure the
Clickonce Requires Assembly Gac
Publish Status for the assembly listed in the error is set to ‘Include' Like this:Like Loading... Related Explore posts in the same categories: Uncategorized This entry was posted on January 2, 2009 http://stackoverflow.com/questions/11505535/unable-to-install-or-run-the-application-click-once at 4:38 pm and is filed under Uncategorized. You can subscribe via RSS 2.0 feed to this post's comments. Tags: Assembly Error, C#, Copy Local, GAC, Microsoft, Microsoft Report Viewer, Visual Studio 2008 SP1 You can comment below, or link to this permanent URL from your own site. 4 Comments on ""Unable to install or run the application. The application requires that the assembly be https://ablogontech.wordpress.com/2009/01/02/unable-to-install-or-run-the-application-the-application-requires-that-the-assembly-be-installed-in-the-global-assembly-cache-gac-first/ installed in the Global Assembly Cache (GAC)first."" Bob T. Says: February 9, 2009 at 7:45 pm You are the man. I had the same problem with VB 2008 Express and made the Office Core assembly true. I also changed two of the publishing choices from automatic to include, not sure of if I needed to but ran the install again and worked. Now I can send a Beta to my client and he can look at the program. Thank you. Reply james igoe Says: May 25, 2011 at 12:14 pm Thanks. Clearest fix found. Everything else was just confused. Reply Bill Dickinson Says: August 10, 2011 at 5:34 pm Interesting. I have all these settings as described, but still get an error message. I added a new, in-house-developed assembly to my click-once application, which up until now, has installed just fine for years. Any ideas??? Reply Bill Dickinson Says: August 12, 2011 at 10:28 am Ok, our case was slightly different from those described already. But, others may encounter it and wonder what's going on, so here's what happened to us (abbreviated): 1. Application A references class library assemblies B and C. 2.
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV https://msdn.microsoft.com/en-us/library/yf1d93sz(v=vs.110).aspx Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Application Essentials Application Domains and Assemblies Assemblies in the Common Language Runtime Assemblies in the the application Common Language Runtime Global Assembly Cache Global Assembly Cache Global Assembly Cache Assembly Benefits Assembly Contents Assembly Manifest Global Assembly Cache Strong-Named Assemblies Assembly Security Considerations Assembly Versioning Assembly Placement Assemblies and Side-by-Side Execution TOC Collapse the table of content Expand the table of content This documentation is archived the application requires and is not being maintained. This documentation is archived and is not being maintained. Global Assembly Cache .NET Framework (current version) Other Versions Visual Studio 2010 .NET Framework 4 .NET Framework 3.5 .NET Framework 3.0 .NET Framework 2.0 .NET Framework 1.1 Each computer where the common language runtime is installed has a machine-wide code cache called the global assembly cache. The global assembly cache stores assemblies specifically designated to be shared by several applications on the computer.You should share assemblies by installing them into the global assembly cache only when you need to. As a general guideline, keep assembly dependencies private, and locate assemblies in the application directory unless sharing an assembly is explicitly required. In addition, it is not necessary to install assemblies into the global assembly cache to make them accessible to COM interop or unmanaged code.Note There are scenarios where you explicitly do