I have published a WinForms application from Visual Studio 2010. It uses .NET 4.0. in the prerequisite dialog in Publish pane I selected .NET 4.0 Client Profile and Windows Installer 3.0. After publishing application to disk, I migrated it to client's computer which first installed .NET Client Profile and after reboot it gave following error message:
Unable to Install or run application. The application requires that assembly, Microsoft.ReportViewer.Common version 10.0.0 in global assembly cache first.
After this message the installation process exits. I'm using .NET's report in my project (not Crystal Reports).
You have to deploy the ReportViewer controls separately.
Check here on MSDN for more information: Deploying Reports and ReportViewer Controls
The ReportViewer control redistributable is a self-extracting file named ReportViewer.exe that includes an .msi and other files. You can find ReportViewer.exe at the following location:
%PROGRAMFILES%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\ReportViewer\ReportViewer.exe
You can also download it from the Microsoft Download Center.
[ . . . ]
The type of control you are using
determines where ReportViewer.exe
should be run.
For ASP.NET applications, run
ReportViewer.exe on the Web server
that hosts your application. This must
be done by a server administrator.
For Windows Forms applications,
include the controls as an application
prerequisite so that they are
installed automatically with your
application. You can use the
bootstrapping application to automate
this step:
Open the project properties page.
Click Publish, and then click
Prerequisites.
Select Microsoft Visual Studio 2010
Report Viewer, and then click OK.
Publish the application.
During application installation, a
check is performed on the local
computer to see if ReportViewer is
already installed. If it is not
installed, the Setup program will
install it.
I guess this is probably a new VS2012 feature, but you now can deploy Report Viewer (and the SQL Server CLR Types) with Forms / WPF click once installations.
Open the project properties page.
Click the Publish tab, and then click the Prerequisites button.
Select Microsoft Visual Studio 2012 Report Viewer, and SQL Server
CLR Types then click OK.
Make sure that the Download prerequisites from the component
vendor’s website option is checked. This is the only supported
option. Then, click OK.
Click the Options button.
In the Deployment tab, specify a deployment Web page and select the
Automatically generate deployment web page after ever publish
checkbox.
Click OK and publish the application.
look at this: Running ReportViewer.exe
both we are gave you same link. it will help you
Download and install Microsoft Report Viewer 2012 Runtime CTP from following url...
http://www.microsoft.com/en-in/download/details.aspx?id=27230
I had same problem but it solved after install the above...
Thanks...
I had the same problem for months, one machine cat v.11 installed (manually by adding some components) and another had v.10 (from the ms framework itself), when I did the publish from my machine, it gave the error.
here is how I fixed it,
In Nuget, there are 2 packages,
Microsoft.ReportViewer.Windows (Microsoft.ReportViewer runtime 2012) and
ReportViewer.Common 10.0
I installed them both, now its working quite all right
Open project properties Alt+Enter.
Click on publish tab.
Click on prerequisites select Microsoft visual studio report viewer.
visit this website for more detail
https://msdn.microsoft.com/en-us/library/ms251723.aspx
Related
Where is the Odoo Studio code? Is it part of the Odoo Enterprise code on Github (which I have access to)?
Is there something I need to enable or add to the project so I see the Studio?
Currently when I run the Odoo Community code, (with the addons path in odoo.conf set correctly first to the enterprise directory) I see no Studio option in the header.
So two questions:
Where is the Studio code and how do I access it?
What do I need to do so I see it, when running the Odoo code from Eclipse?
1) Studio code is the one of the module inside the Odoo Enterprise addons with named "web_studio". For that you need the access of the Enterprise addons.
2) After installing the module web_studio you can get the one icon on top right corner before logged in user name like tools with tool tip "Customization". By clicking on that you can start the Studio for manage any changes inside the current screen.
I hope you are getting both of the answer correct fully.
I have downloaded VS 2015. I want to integrate SAP Crystal Reports in VS 2015 Enterprise Edition. I have also downloaded the MSI file of the latest SAP Crystal Report edition and installed it. However, I am not able to see the Crystal Report Viewer.
I had a very difficult time finding this particular download page and the appropriate download link on that page for Visual Studio 2015 (I also have Enterprise but I don't think that matters too much, if at all for this). The link is provided below, the download link is titled, "Support Pack 15 (v.13.0.15.1840)".
http://scn.sap.com/docs/DOC-7824
So I did the following:
1.) I had to uninstall two Crystal Report applications that I had previously installed (one was an update for it I think).
2.) Then I shutdown VS2015.
3.) Then I ran the downloaded executable, it installed fine and I installed the 64 bit run-time feature for Crystal Reports.
4.) Then I made a mistake and tried opening VS2015 afterwards, it crashed repeatedly.
5.) After restarting the PC, I have no more errors and I now have the crystal reports icon in the Report's category when adding a new
item to my Web Application project. It also allows me to use the wizard.
Hope this helps!
You can download it from:
http://scn.sap.com/docs/DOC-7824
Download "Crystal Reports", click in the link "Support Pack 16" ((#1 in the picture)) for developers.
Download the "Run time", clic in the link "MSI 32/64 Bit" ((#2 in the picture)) for the clients.
Finally, restart your PC.... open your visual studio 2015 again and you will see "Reporting" option for Crystal Reports when you add a new item.
Happy code!
You can download it from this link http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_13_0_18.exe
After installing, Open Visual Studio,
Create a folder for the reports
Right Click and Add new Item
Go to Reporting
You will see Crystal Report on the list. Select that and start designing.
I have inherited an SSRS solution that I can't seem to work with. I sat down with the previous owner briefly and he showed me where in TFS to find the solution. The also opened up a few of the RDL files and attempted to give me the gist of modifying a report. Every thing seemed straight forward to me during that session.
Now the original developer is gone and I now have access to the code in TFS. Whenever I try to open one of the RDL files, it opens it up as an XML document instead of opening it in the designer.
I have Visual Studio 2008 and SQL Server 2008 Management studio installed. Any thoughts on what I may be missing like service packs or hot fixes?
Re-run the SQL Server 2008 installer on your machine. You need to install the Business Intelligence Developer Studio component, or whatever it was called in '08.
If you don't have access to an installer, find the SQL Server Express with Advanced Services download (whatever year you need, just make sure it's the "Advanced Services" - here's 2008: http://www.microsoft.com/en-us/download/details.aspx?id=1842 ), and run that; it will also provide an option for BIDS.
I'm working on a VSTO add-in for Outlook, versions 2007-2013and minimum .Net version is 4.0. In my project I have a couple of referenced libraries. When I deploy the add-in via MSI (built via Wix) the add-in itself is loaded into Outlook but, the referenced libraries are not available.
It works fine on my development machine so I'm assuming it is a trust issue of some sort. I am uncertain as to what needs done to have the included libraries themselves be trusted. Any help is appreciated.
Are you using VS setup project for addin deployment? If so, you might want to try
Right-click setup project icon => Add => Assembly...
to add your external libraries.
Regarding the trust issue, please take a look at these articles on MSDN. Inclusion list might also be helpful in your case.
Also, to test deployment on your development machine, I'd suggest you clean your project/solution first
Right-click Project/Solution icon in Solution Explorer => Clean
then deploy and install your addin onto your machine.
My add-in targets Outlook 2007 and was built using C# with Visual Studio 2010. I have run into problems deploying this to different target machines by means of the SETUP.exe and "manifest" built by the Publish Wizard of Visual Studio.
My latest attempt to get this deployed to a target PC (i.e. one typical of other users where this will be deployed and lacking my development environment) gives strange problems:
the add-in installs OK (i.e. Setup had no complaints; program appears properly in Control Panel)
visiting Tools -> Trust Center -> Add-ins shows that my just-installed add-in is Inactive
clicking Go.. for the Manage COM Add-ins dialog & checking the box for mine then the Add.. button fails
a window looking like a browse dialog box titled "Add Add-in" comes up with "No items match your search" in the right-hand pane; at the bottom of this window is an empty textbox labeled "File name:" and a choice of "Executable Files" or "All files" for a file type. The add-in remains "inactive".
It is not clear to me what this dialog needs at this point to make it "active" (Load at Startup was part of the choices here).
NOTE:
The 2 projects in this solution were compiled for a "target framework" of .Net 3.5 resulting in references to DLLs such as Microsoft.Office.Tools.Outlook.V9.0 and his companions (I guess that is "VSTO 3.0 ??).
This solution launches Outlook properly on the development PC and the add-in is loaded successfully and runs as expected (against Outlook 2007 and/or Outlook 2010); so this seems related to deployement only.
Could there be a bug in the stuff built by the Setup wizard that comes with Visual Studio 2010? I read somewhere that the "manifest" can be "corrupt".
EDIT-UPDATE 3/31/2011:
I think I found the answer. I believe by using the "Publish Wizard" in VStudio which produces a SETUP.EXE, I was trying what is called "ClickOnce" deployment. Secondly, this addin for Outlook is NOT a "document level" addin but instead a "machine level" addin. Given these discoveries of better terminology, I found this at http://msdn.microsoft.com/en-us/vsto/ff937654.aspx:
"You can use ClickOnce to create and install self-updating applications with minimal user interaction. This has an automated mechanism for easily distributing updates to your application. However, ClickOnce is not capable of deploying components that require administrative privilege such as machine level add-ins. For solutions that require administrative privilege you can use Windows Installer to deploy a Visual Studio Tools for Office customization."
So, I will try to make a Windows Installer. Any confirmation would be appreciated.
I am confident the ClickOnce style of deployment will NOT work for my machine level add-in for Outlook 2007. Therefore, I am answering my own question by stating only that this requires a Windows installer (and setup) that can built with the properly chosen Visual Studio template.
The sad news is that in my testing of said installer .msi and associated setup.exe for the pre-requisites the install to my target machine went well but when I test the operation of the addin itself inside Outlook I get a terrible APPCRASH event in Outlook.exe:
Problem signature:
Problem Event Name: APPCRASH
Application Name: OUTLOOK.EXE
Application Version: 12.0.6550.5003
Application Timestamp: 4d10fbc4
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6001.18215
Fault Module Timestamp: 49953395
Exception Code: e0434352
Exception Offset: 000442eb
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
LCID: 1033
Brand: Office12Crash
skulcid: 1033
So the answer is that ClickOnce is not appropriate. The .msi appears to properly install the add-in but at runtime it blows sky high. Remember the addin works properly at runtime when launched via Visual Studio. Why does deployment have to be so damned difficult?