After installing, uninstalling, reinstalling, cussing, taking periodic naps and then tearing up just a little, I finally gave up trying to install Web Deploy v3.6 with Visual Studio 2015, it just isn’t going to happen in my lifetime.
Just in case you run into this same issue, the information below may help you.
When attempting to install Visual Studio 2015 and Web Deploy v3.6 (as administrator), I received the following errors via the interface and logs regarding Web Deploy:
- Registry key not found. Key = ‘SOFTWARE\Microsoft\IIS Extensions\MSDeploy\3’; variable = ‘webdeploy_x64_en_usmsi_902_DetectKey’
- There is a problem with this windows installer package the script required for this install to complete could not be run.
After following 809 centillion online suggestions to no avail I finally gave up and instead installed Web Deploy v3.0 with Visual Studio 2015 and all is right with the world. As of August 2017, Web Deploy v3.0 is still available for download here: https://www.microsoft.com/en-us/download/details.aspx?id=30436
I had Crystal Reports on an old server. It was time to make a decision regarding how to get the reports over to a new server quickly and at the same time avoid purchasing more software and enduring installations, testing, etc. For now, I decided to put the reports in Visual Studio. If you find yourself in a similar situation, then the information below may save you some time. This is how I did it:
- Closed all applications on my pc (Windows 7, 64-bit)
- Installed this: http://scn.sap.com/docs/DOC-7824 (Support Pack 16, I MUST INSTALL the exe, NOT the msi or it will not properly integrate with Visual Studio), at the end of the installation it asked me if I would also like to install the 64 bit, I said no and all was well.
- Rebooted pc
- Copied this folder: C:\Inetpub\wwwroot\aspnet_client\ into the directory with my Visual Studio solution (I created a solution in Visual Studio called crystalReports) on my pc and inside the solution I imported the crystal report rpt file then I created an aspx file where (from the Toolbox > Reporting) I dragged a “CrystalReportViewer” and “CrystalReportSource” onto the code in Design view. It will look like this:
” <CR:CrystalReportViewer ID=”CrystalReportViewer2″ DisplayToolbar=”True” DisplayStatusbar=”true” runat=”server” AutoDataBind=”true” />
<CR:CrystalReportSource ID=”CrystalReportSource2″ runat=”server”></CR:CrystalReportSource> “
The code behind has a Page_Init like this (if you leave out the init then you will most likely see issues when you try to view multiple records within the crystal report):
protected void Page_Init(object sender, EventArgs e)
ReportDocument reportdocument = new ReportDocument();
ConnectionInfo connectInfo = new ConnectionInfo()
ServerName = “servername\\SQLEXPRESS”,
DatabaseName = “dataInReport”,
UserID = “cheesyPoofs”,
Password = “chess”
foreach (CrystalDecisions.CrystalReports.Engine.Table tbl in reportdocument.Database.Tables)
tbl.LogOnInfo.ConnectionInfo = connectInfo;
CrystalReportViewer2.ReportSource = reportdocument;
- Run the aspx page and you should see the embedded crystal report running properly on your pc
- You also need to install Support Pack 16 on whatever server you plan to run this Visual Studio application on so remember to do this before you publish your application to a server
- You also need to copy this folder: C:\Inetpub\wwwroot\aspnet_client\ to the same location on the destination server
- You might need to download the individual drivers to get a specific report working, I didn’t have to do this but it could be a possibility for you (i.e. https://dev.mysql.com/downloads/connector/odbc/3.51.html)
- Misc Note: Cross reference web.config vs your ODBC. NOTE DSN entries mean you need an existing connection with that name.