ClickOnce: Unable To Install Or Run The Application, Requires Microsoft.Vbe.Interop 14.0 To Be Installed
Apr 15, 2011
Just got this message today on user machines when pushing out an update to a ClickOnce VB.NET application.No new references have been added, just some bug fixes.
System Update Required Unable to install or run the application. The application requires that assembly Microsoft.Vbe.Interop Version 14.0.0.0 be installed in the Global Assembly Cache (GAC) first.Note that this is only happening in XP machines, not Win 7.
I have designed and published my small created app with WINDOWS FORMS using VB 2010 EXP on Windows 7. I can only install the app on the machine that I used to develop the app.I want to install the app on another computer but I cannot. I usually have error reports.
Example:Unable to install or run this application. This application requires Microsoft Common Language Runtime 4.0.3 to be installed on your computer.
what can I do to be able to install the app on a different computer which does not have .Net and does not have visual basic 2010 installed.
So I'm guessing it has something to do with the fact that I don't have office loaded on my computer. Now I have another laptop, with office that I loaded this project on, and it works fine. So do I have to load office on this computer, or can I just reference something?
I am working on a legacy VB.NET application that uses Microsoft.Office.Interop.Word, with Office 2003 installed on the server. When I publish my site, even though my config file clearly shows v11: The site will crash saying v12 couldn't be found: Could not load file or assembly 'Microsoft.Office.Interop.Word, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Note: I currently have Office 2003 & 2007 installed on my dev machine, also, when looking @ references I am given the option of selecting v11 or v12 (so v11 is def. there). Within a page on the site the page does an import statement for Microsoft.Office.Interop.Word. Is it possible to specify the version at this point, or any way to force it to use v11 without me uninstalling my v12?
I have Visual Studio 2010 and a VB Project that had a reference to Microsoft.Interop.Excel 12.0. Well recently I changed the reference version to 14.0. That was actually a mistake and now I need to bump it back down to version 12.0. However I get this error in my project now...
Project 'MyProject' requires a reference to version '14.0.0.0' of assembly 'Microsoft.Office.Interop.Excel', but references version '12.0.0.0' of assembly 'Microsoft.Office.Interop.Excel'.
I tried removing references and adding the com object to, but no avail.
When using clickonce deployment, where are the application folder/files installed? I have found a data file in Owner>AppData>Local but the actual program files evade me!!
I have been trying to use vb2008 to automatically update CustomDocumentProperties fields that I have set up within a pro-forma document. I can load the Word application and word document without problems.I want to update the CustomDocumentProperties fields with data read from a dB. To do this I am assuming that I need to iterate through the CustomDocumentProperties fields within the word document and when one is "found" that matches the data I wish to merge then assign the dB value to the field.The problem is that I am getting an exception error when I try to reference the document customdocumentproperties
"Error : Unable to cast the COM object of type 'System._ComObject' to interface type 'Microsoft.Office.Interop.Word.CustomProperties'. ...... "
my code looks like;
Dim WordApp As Word._Application Dim odoc As Word._Document Dim BContinue As Boolean = True
I have created an application in VB.Net 2010 and am using an Access 2010 db. Connecting to this DB I use the Provider= Microsoft.ACE.OLEDB.12.0 and it works fine on my machine. This was a recent update from using Jet as that provider was having issues on client Win64 computers that had Access 2007 or 2010 installed.Basically my issue is that I get the error that Microsoft.ACE.OLEDB.12.0 is not installed when I try to run the application on the client.
The problem however, is that I do not want ask the users to install Data Access Objects in addition to .Net 4.0. I want a simple install that they can run and upgrade to .net 4.0 if they need to. The above thread states a solution as "You can also consider to use ADO.NET object in System.Data.OleDb namespace to connect to the Access database instead of the Provider. In my opinion, this is the best choice since the ADO.NET provides you the powerful data access objects." This sounds like a great option, however I cannot find any way to install the ACE dll and get it to work on the client.what do I need to include in the client installer to get my application to run on systems without Access installed? Do I just include the ACEODB.dll or is there something else that needs to be done?
I'm using VS 2010, and I did a project using VB and a database in Access. The problem is that when I try to put that "application" on other computers, sometimes, is not working. I thought it can be because on these computers they don't have access, but on one computer, is running another app which is using Access and there is no Access installed. How can I check if my application requires Access to be installed or not?
Here is a example of how I did the connection:
Public AccessOLEDBConnString= "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=" & myfullpath & ";Jet OLEDB:Database Password=password"
Function getConnection() As OleDb.OleDbConnection
[CODE]...
And when I want to have access at the data I'm doing like this:
Using VB.Net 2010 (not Express)I'm at vthe point where I'm starting Beta Testing. I createds the build and then a publish (to a network share).Now the testers are getting an error during install complaining that "System Update Required"...Unable to install or run the application. The application requires that assembly Microsoft.VisualBasic.PowerPacks.Vs Version X.X.X.X be installed in the Global Assembly Cache
I am trying to figure out what all the files do so that I can use Inno Setup to create an installer. y plan was to install all the files to a temp folder. Then run setup.exe.However, I was not sure what to do about the uninstaller? Inno will want to uninstall as well, which I think I can have it run a file on uninstall. So I was thinking maybe I should put some or all of the files into a permanent folder instead of
To install my application on a remote machine it gives me an error reading..Unable to install or run the application. The application requires that Assembly Microsoft.synchronization.data.server version 2.0.0.0 be installed in the Global Assembly Cache first..I am running vs2010 and I am deploying on a windows XP Service Pack 3 machine. [code]
Unable to install or run this application. The Application requires the assembly My.SQL.Data Version 6.2.3.0 be installed in the Gloabal Asseembly Cache (GAC) first Can someone please explain what this means?
I've made a program but when others try and run the installer they're getting the error "unable to install or run the application.The application requires that assembly Microsoft.vbe.Interop Version 12.0.0.90 be installed in the Global Assembly Cache first.
My college said he had problems creating a ClickOnce deployment because he could not reference one of the 2 Interop DLLs in his visual studio. I find this rather hard to believe so I'd like some input from experts. is it true you can only deploy the dlls that are referenced in your project?
When I try to install an application to another user's computer I receive a message box that says "Unable to run or install application. The application requires that assembly Microsoft.SqlServer.Pipelinehost version 9.0.242.0 be installed in the global assembly cache (GAC) first.A key feature of the app is to export data from sql server to an excel spread sheet so I have the following import statements
I have a project which opens a simple Excel file and populates it. It was working fine until this morning, when it has suddenly started giving me the error above: 'Application' is ambiguous in the namespace 'Microsoft.Office.Interop.Excel'.I haven't changed any project references, or anything within the file itself. The references include Microsoft.Office.Interop.Excel. The imports statement is there: importsMicrosoft.Office.InteropThe object declaration is also complete: Dim xl AsMicrosoft.Office.Interop.Excel.Application which is the line that's giving me the error!
I am fairly new to programming and I am trying to create a MS Word add-in to add an xml file into the WordprocessingML package of docx files.I am currently having trouble with Microsoft.Office.Interop.Word.Application.ActiveDocument", used:Dim currentDoc As Document = Microsoft.Office.Interop.Word.Application.ActiveDocumentbut I keep getting the error: "Reference to a non-shared member requires an object reference" there.
I have some jpeg images that are added to my application. The Copy To Output Directory property is set to Copy Always. Running from Visual Studio the images are accessed and if I install the application to a drive on my computer directly the images are accessed but if I publish my application to my web site and install via the publish.htm page then the images are never accessed regardless of what I have the Build Action set to.
If the Build Action is set to Content then it won't even install because I get an error that says the computed hash for the images doesn't match the manifest. I've tried all the different Build Action options without success. For Build Action = None, Compile and Embedded Resource I don't get the error I do for Content but the jpeg images aren't accessed. [code]....
My clickonce app has the following pre-requisites: Windows Installer 3.1 .NET Framework 3.5 Microsoft Visual Studio 2008 Report Viewer Microsoft Visual Basic Power Packs 3.0 SQL Server 2005 Express Edition SP2 (x86) The application has been successfully installed on more than 30 computers. All but 2 computers, have had installation problems.
For awhile, one of the two computers in question, would not resolve installation of SQL server 2005 Express edition. It would go through the motions of downloading the program and then attempting an install and after a good 30 minutes, an error would show up indicating that the installation had failed. The user continued to have a nuisance error pop up appear when he'd log into his computer.Long story short, I resolved that problem. So now all of the pre-requisites are installed and confirmed as successfully installed. The clickonce application does not install however. The following log file was created as a result of this error:
PLATFORM VERSION INFO Windows : 5.1.2600.131072 (Win32NT) Common Language Runtime : 2.0.50727.3053 System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000) mscorwks.dll : 2.0.50727.3053 (netfxsp.050727-3000)
I have written a program and deployed using clickonce to all desktop users. Additionally, the program is also installed (non clickonce) on a terminal server. (For security reasons, these users cannot install on their desktops). I need to add some code to the current program but only need this code to happen if it's being run as a Non ClickOnce Application. Does anyone know how to determine if the running version is a clickonce or not? Is there something in System.Deployment.Application that identifies?
My application is small, I intend to use the installer that comes with VS 2008 Prof.Edition, or ClickOnce.I'm wondering which is better, I need to include a copy of the .NET framework 2.0 in a package, and have it installed simply, and also be easy to uninstall.
I am using VS 2005 under Windows 2000, and have a requirement to interact with Excel.I figure the easiest way to do this is by using the PIA from microsoft so I can just Import the Excel Interop into my project.So, I got local admin rights and downloaded and installed the PIA. I then found that my version of office was not SP1 so I upgraded to SP3 and then installed the PIA again.However, back in my project I have added a reference to Excel, but I do not see "Interop" under Office, I just see "Core"This means I cannot use : Imports Excel = Microsoft.Office.Interop.Excel.Also, when I check references again after restarting, I do not see any Interop references under .NET or COM.Why is it that Interop just doesn't seem to be installed (I see it under Add/Remove programs)
I have a ClickOnce app that has been working fine for a couple months, until a day or two back some internal politics borked the server. The result of this was that the path for ClickOnce during install changed just slightly at one intermediate level. It used to have /is/ in the path, and the is has changed to something else. I changed everything I could find, including recreating the whole target directory in IIS on the server. However, when I publish, though the link is correct, installation is failing. The log shows that, after checking and installing some prerequisites, the installation is attempting to go back to that /is/ path to find the app for installation.
Can anybody suggest where that invalid path is located? I have gone through every property I can find in Project|Properties, and they are correct. I have looked in App.config, and that is correct. Where else should I be looking?
I have finally finished an application which works really well on the PC upon which I developped it using VB 2008 Express.My problem is that when I publish it and try to install the ClickOnce output files on another PC (tried two so far, both WinXP) I get a missing files error. There is an error output saying that downloading the .exe.manifest file did not succeed. Unfortunately the error detail is confusing and does not seem to indicate exactly which files are missing.On both of the PC's that I tried I was prompted io install .net 3.5 SP1, which seemed to have been successful. The inference is that it is not a .net file that is missing.
I have a question to ask you. All of the programs that I made always worked perfectly in my PC. But, whenever I test it on another PC, it requires a thing like... Microsoft .NET Framework Version 4. Which is really annoying, cuz that thing installs in 15 minutes. I mean, can I do something about this? Is this common?
