I am trying to deploy a VB.Net application using the built in Click Once.
When a User tries to install the application they receive the following error message.
http://i.imgur.com/6ifvdKM.png
The machines they are trying to install to are Windows XP SP3 so I cant understand why I am getting this error.
Any help would be appreciated.
You should try the following steps:
Compile your program and copy the whole bin\Release folder (output directory) to the target system. Does your program run if it's not distributed via ClickOnce?
Build a simple "Hello World!" program and distribute it via ClickOnce. Can this basic app be installed on the target system by running the ClickOnce installer?
Even though this should not be a problem on any system running a later Version of Windows than Win2k, have your tried to just install Microsoft Data Access Components (MDAC) 2.8 SP1?
By doing so, you should be able to determine if your issue is either ClickOnce- or Application-related.
actually i working on a Application that is going to be build for windows 8 surface and desktop but we want this not to be on store but as a business solution. but i want my app to be tested by testers but i am not getting how to provide then my full package so that they can test it. any idea is appreciated.
In Visual Studio 2012, with your Windows Store project selected, go to Project -> Store -> Create App Package...
Tell it that you do not want to upload the app package.
This will create a folder for your app that includes the .appx, the .cer, and a .psd (PowerShell script). Zip up this folder and send it to your testers. They just need to run the PowerShell script by right clicking it and clicking "Run in Powershell...". It will prompt them for a Developer's License (which they will need), but this will be retrieved automatically after signing in with their development account.
I have a small windows forms application created in Visual Studio 2012 that uses ReportViewer version 11.0.0.0.
The application target framework is .NET 4.0 and its deployment method is ClickOnce
On my PC it installs but on client machines, intallation fails with error
the application requires that assembly microsoft.reportviewer.processingObjectModel version 11.0.0.0 be installed in the global assembly cache first.
On the client machines, i have installed
.NET 4.0
ReportViewer 2010
Microsoft Report Viewer 2012 Runtime CTP
SQLSYSCLRTYPES.msi
in the project application files settings, i have set microsoft.reportviewer.processingObjectModel publish status to Include(Auto), in the references i have also set its Copy Local property to True.
what am i missing?
I have even followed the instructions here http://msdn.microsoft.com/en-us/library/ms251723.aspx
Here is (arguably) the best way to deal with this issue... without downloading or installing any extras. This worked with Visual Studio 2012 (Ultimate)
Goto the main project within your solution(default/statup project)
Right Click and Click Properties / Select "Your Project">> Project>> Properties
Click on "Publish" Tab to see publishing options
Goto "Install Mode and Settings">> Click "Application Files" and Dialog opens
Go down and look for the items set with "Publish Status" > Prerequisite
You will find ReportViewer and Several Other Files set to Prerequisite
Change all the Publish Statuses to "Include" in the drop down
I know you only need the ReportViewer Only but this will eliminate other potential problems I came across
Now all the required files will be added to your installation setup good to go!
For interest, you can change include a desktop icon under "Install Mode and Settings">>Options>Mainfests>Create Desktop Short Cut
you are missing the ProcessingObjectModel.dll file find the version 11.0.0.0 in gac assembly C:\windows\assembly\GAC_MSIL\Microsoft.ReportViewer.ProcessingObjectModel and add it to bin dir.
We had the same issue, but the thing is, its automatically adding it to the references (microsoft.reportviewer.processingObjectModel), if u EXCLUDE it from the publishing properties(properties->publish->application files), It might fix it.
A better option would be to install the Microsoft Report Viewer 2010 SP1 Redistributable Package at:
http://www.microsoft.com/en-us/download/details.aspx?id=6610
Your users will need to have this package installed as well. If you just copy and paste a MS DLL, you'll have to redeploy it every time you upgrade your application.
If you are using WinForms, to me it seems pointless to worry about installing this DLL in the GAC when it's being used for a report viewer that is deployed via click-once. This isn't a big file and you're probably using it as a report viewer control on a form, nothing more. One possible solution is to do the following:
In Visual Studio, go to the reference in your project for the assembly Microsoft.ReportViewer.ProcessingObjectModeland locate the file path to the folder for that assembly. Mine was version 12 and so my file path was C:\windows\assembly\GAC_MSIL\Microsoft.ReportViewer.ProcessingObjectModel\12.0.0.0__89845dcd8080cc91
Copy the file path of the folder the assembly is in and remove the reference from your project (right click the reference and select "Remove").
Win + R to get a 'Run' prompt. Paste that folder path in there and execute to jump right into the folder of that DLL.
Find the DLL, it should be the only file in that folder, and copy it to your Visual Studio project folder. You shouldn't care about 100kb of extra space on your drive consumed, and I don't think this DLL is one you'll need to update.
Back in Visual Studio, right click References, Add Reference, and browse for that DLL in your project folder. After adding the reference, make sure that the Copy Local property is set to true.
Clean and rebuild, test the application on your local computer, than Deploy your ClickOnce again.
Now when users install your application with ClickOnce, the reference will not refer to the GAC at all and there won't be any need to rely on the prerequisite check/installation process for this DLL because you have included it directly in your published application.
It depends on the setup type you are using but basically, it means the required library is missing from your server or computer. To enable the application to download from the server (In a client-server architecture), you need to include the file(s) in the project.
Go to your application option and locate the "Publish" tab
Click on "Application files"
In the ensuing dialog, select to include all the libraries you want included (or that are required to run your application on the client machine and click "Ok")
Build your application and then publish to the server.
I hope this works for you, it worked for me in Visual Studio 2010 Professional
In case of Windows 10 it won't work installing Microsoft Report Viewer 2010 SP1 as describe by user1236560. First you need to install Prerequisites for SQL Server Management Objects (SQLSysClrTypes.msi) need to choose between x86 and x64 depending on your hardware. You could find it on: http://origin.www.ms.akadns.net/downloads/en/details.aspx?FamilyID=16BC778C-357B-46E9-8356-D575903AC831
After that you need to install MICROSOFT® REPORT VIEWER 2012 RUNTIME that you could find on: https://www.microsoft.com/en-us/download/details.aspx?id=35747
Both of this package will have to be installed.
I encountered this error
System Update Required
Unable to install or run the application. The application requires that assembly
Microsoft.ReportViewer.ProcessingObjectModel Version 11.0.0.0 be installed in the Global Assembly Cache (GAC) first.
Please contact your system administrator.
this error popped out when installing an application made from Visual Studio
meaning I am one of the client
I have Visual Studio 2015 and a Microsoft SQL Server 2014 and didn't know about Crystal Reports and other related stuff to it. I do check the version of my .NET Framework which is version 4.6.2.
I have several extension files and distributable files downloaded and yet doesn't solve my problem.
I do not know if I solve the problem generally but I do become successful in installing the application
so I downloaded and installed the ff:
SAP Crystal Report for Visual Studio 2015(latest, just to make sure)
Microsoft System CLR Types for Microsoft SQL Server 2012
Microsoft Report Viewer 2012 Runtime.
the problem took me about 2 days to trouble shoot, Be careful on downloading and installing extension files and distributed files cause it will munch some space too.
The Best answer is:
Here is (arguably) the best way to deal with this issue... without downloading or installing any extras. This worked with Visual Studio 2012 (Ultimate)
Go to the main project within your solution(default/statup project)
Right Click and Click Properties / Select "Your Project">> Project>> Properties
Click on "Publish" Tab to see publishing options
Go to "Install Mode and Settings">> Click "Application Files" and Dialog opens
Go down and look for the items set with "Publish Status" > Prerequisite
You will find ReportViewer and Several Other Files set to Prerequisite
Change all the Publish Statuses to "Include" in the drop down.
I know you only need the ReportViewer Only but this will eliminate other potential problems I came across
Now all the required files will be added to your installation setup good to go!
For interest, you can change include a desktop icon under "Install Mode and Settings">>Options>Mainfests>Create Desktop Short Cut
It reduced all of my head aches.
I am working on a dashboard related project using the MS BI stack integrated with SharePoint. I have a configured POC server running on Windows Server 2008 R2, SQL 2012 and SharePoint 2010. I am trying to run one of the MS tutorials that I have already completed on the MS virtual labs in a completely 2008 environment but doing so within my SQL 2012 / SharePoint 2010 environment and this requires I use the .dep file to set the tutorial up. When I first tried to run it I got the windows doesn't know which program to run it with but since the server is in a sandboxed area without net access it cannot search the web for the correct program. In the tutorial it mentioned the file ran via the command prompt so I tried opening it with that and unfortunately nothing happened, but I forgot to untick the always associate box so basically I now have two issues.
First is getting the .dep file back to having no default associated program to run with or finding out what actually is the correct one and the second is to actually get the required files I need to run the .dep file and set-up the environment for the tutorial. Unfortunately MS does not have a nicely detailed list on this.
I have tried using GPMC.MMC to remove the file association but as it is connected to our active directory the default features do not match up with what the technet article states on doing this and I don't want to cause errors on our active directory. Any advice on how to get this working would be appreciated.
You can try downloading the offline training kit.
This training kit should contain a folder with the name "assets". Into this folder you can find an installation of the software "DependencyChecker.msi". Just do this installation. The installation associates the .dep files with the "Dependency Checker Tool"
Secondarily, you can google around to find "How to install the Microsoft Dependency Checker Tool".
In the next link Microsoft talks about the tool.
http://msdn.microsoft.com/en-us/identitytrainingcourse_silverligthandidentity2010.aspx
I have designed an Application tracking details and I have deployed it. The records are updating the way I need. I want the same application to be used in other three different systems which do not have MS Visual Studio. How can I do it ? Is it enough that I create a similar table in the path I have designed in the other systems and run the Application ?
The probably easiest way to deploy your project would be:
Copy & Paste the whole output from your bin folder to the other machine and make sure the .net framework you used for your application is installed on this machine.
You can also create a Setup and Deployment Project
Open the Solution of your application
File -> Add -> New Project...
Other Project Types -> Setup and Deployment -> Visual Studio Installer -> Setup Project
In the File System Tab right-click on "Application Folder" -> Add -> Project Output and Select "Primary output" from your application project.
(More details about adding files to your setup project: How to: Add Items to a Deployment Project)
If you want to use a copy of the access database on each machine
As you're using an access database. You can mark the include you're access database to your project and set Build Action (in the Property Page) to Content.
Now in the same manner as before rightclick on "Application Folder" and add project output. Only this time select "Content Files" instead of "Primary Output"
Build the setup project and distribute the setup.exe or the .msi file.
If you want to access the same database from each machine
I would advise to store the application on a server which runs independent of your machine so that others can access the database also when your machine is not running.
Change your connectionstring, so that users from other machines are able to connect have a look at this site if you need help with connectionstrings.
As you won't be able to connect to the database with the absolute filepath from other machines, create a fileshare where everyone who should be able to connect has permissions to read/write.
Build the setup project and distribute the setup.exe or the .msi file.
Hope this helps so far.
Why should there be VB language on the target computer? Once compiled(published) you are out of the language environment and the program is in the machine language. In order to publish you have to go to "Build" and "Publish" after opening the program in the language environment. Publish it to a flash drive instead of the C drive. You can do that by selecting the "Browse" option. Once done you can take the flash drive around and install it on most computers that have the .Net files installed. In my experience most windows opss have them.
Just create an Installer after you have written and debugged your program. Install it plus your database on the server computer. If you intend to share the database and its a file-server database such as Ms Access, you will have to make sure that the folder is a shared folder.
Go to all the other computers on the network and repeat your installation. Make a Mapped drive on each computer and configure your database string to point to the mapped drive. If your database a server one like SQL Server, you will need to configure your database access string to point to the Server like so:
\Syl-PC\SQLEXpress.MydatabaseName
I assume that you are familiar with the complete syntax for connecting to databases from Visual Basic using a database provider such as Ole db or the SQL Server Provider.