I am trying to create a bootstrapper package to add Crystal Reports 2011 to my application. I have determined that the location should be c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper. I added the package in the package folder but it does not show up in the prerequisites menu. I have tried rebooting but it still does not show up. I used the package that I downloaded from SAP called CRforVS_clickonce_13_0_3.
Any ideas?
You should bundle the merge module for Crystal Reports 2011 inside your install package. If you include the merge modules they will simply be bundled into a single install.
(It didn't sound like there is a specific reason to bootstrap multiple MSI packages. The merge modules are an easy and reliable runtime deployment method.)
Related
Is it possible to get pug in project for Outlook that is depend on NuGet packages to be installed with Microsoft Visual Studio 2017 Installer Projects? I’m trying to create an installation file for a plug in for Outlook that have a drag and drop functionality dependent on the Easyhook Nuget package. That the plugin have a taskPane with a webbrowser there are drop Outlook e-mail messages as .msg files.
It works to install the plug in but the drag and drop functionality that is dependent on the NuGet package doesn’t work. That I can drop the message but the webpage doesn’t recognize the drop mails as .msg files or even as uploadable files. While if I try with the trial version of InstallShield 2018 Express Edition everything works including the drag and drop functionality.
I tried to do the same thing with Installer Project as with InstallShield. To output I added content files, debug symbols and primary output. Files I added was the manifest and vsto files for the Plugin and the .dll file for the NuGet Package, Easyhook32.dll. I got an error because the content file included the 64bit for the NuGet Package files, and I’m doing a 32bit installation, and also that the Easyhook32.dll file was duplicate, that it seems that the dll file also was added with the content files.
So, I excluded the 64bit files in the plug In project that should be installed and in the installation project I removed Easyhook32.dll files from the files that should be include in the installation. Also then it worked to install the plugin but the drag and drop functionality didn’t work. I also tried to for example not add the content files and just add the Easyhook32.dll and that also made the installation work except the drag and drop functionality.
I can of course also try other installation programs that is able to add NuGet but also are able to be installed from the Internet and also add registry keys and values. That I also have tried Microsoft Click Once installations program and it was easy to create an installation files but it seems like you need a valid certification if you want users to download the installation file from the Internet.
Also, this is the first time I working with type of installation like this ones and with Outlook Add In so I can have missed some obvious solutions. That at the same time english is not my first language so I can also have missed using the correct terminology.
NuGet is a build-time package manager. You'll need to redistribute any required binaries in your installer package by adding them manually. Typically, required binaries from NuGet packages will be copied to your output folder, so you could add them from those paths just like your project output.
According to the question Bundling only part of the prerequisites with ClickOnce a ClickOnce installer can either download ALL prerequisites from the web or expects ALL of the files locally. This seems to be the same for a Visual Studio 2008 deployment project.
As I would also prefer to include only selected prerequisites in an installer archive I was wondering if this is really still state of the art. Will upgrading to Visual Studio 2010 solve this issue or is there any workaround that I overlooked?
So here's an idea that I came up with.
Package the bootstrap installer with all prerequisites except the
.NET framework with "Download prerequisites from the component
vendor's web site" set
Create a small program (batch file or
executable) that is launched instead of the bootstrap installer which
does the following
Check if .NET framework is installed (the bootstrap package files tell you how to check this, e.g. .NET framework is installed if
HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5\1033\Install ==
1)
If yes execute setup.exe -homesite=false which configures the installer not to download any files
Execute setup.exe
Comments welcome!
You can package the prerequisite and set a download URL and put the prerequisite there. Then when the prerequisite is installed by the bootstrapper, it will download it from the URL instead of having to include it in the deployment package. This means, of course, that you have to set up your own bootstrapper package every time you want to do this, but it does work.
After compiling a Visual Studio setup project: there are two files produced: application.msi and setup.exe
If I run application.msi, the new version is not rewritten to the old version. It is likely to run setup.exe for all of the cases. That made confusion if I give two files to the clients. How can I made just one file?
The Setup.exe file is a BootStrap file used to check for the prerequisites that you setup in your Setup Project's Prerequisites Dialog. The MSI package itself is what determines the applications installation parameters. You should have Remove Previous Versions as true and make sure that your application's Assembly version has been incremented by at least the Build Number, otherwise if you are updating only the Revision number it will not be over written. The Assembly Version information Format is as follows. Major.Minor.Build.Revision. Make sure that you also change your setup projects Version number also.
You can package the MSI with setup.exe into a single self-extracted archive and launch setup.exe after it's unzipped.
I have an update to third party .DLL that must be installed onto my clients' computers. We currently employ automated installs via MSI that are created in Visual Studio 2010
Unfortunately, the third party .DLL was versioned incorrectly and file version of it was not increased by the provider (they only increased assembly version). The third party provider is Microsoft, so waiting on them to fix the issue is not realistic. We need to get the new .DLL to people now and within one MSI update. Right now, MSI update is not overriding the .DLL
Is there a way within VS2010 Setup project to force override a .DLL even if the file versions match?
If you are willing to do msi postbuild tweaking you can hit the File table and do "version lying". Another thought is to not put that DLL in your install. Find an installer from Microsoft ( if it exists ) that you can put into a bootstrapper or create your own installer and use AMUS instead of OMUS for the version rules.
Can't you just add the file to your installer as a 'file' and install it with the other files? Don't set it as project output, or any of the canned install actions. Go to the file portion and right click the "Application Files" folder, and say > add file. Navigate to the file that you want and choose it.
I have written an application that interfaces with QB Pro in VB6. I would now like to deploy it to the client's system. What are the DLLs and/or MSMs that I should include in the installer?
I am using the Visual Studio Installer to create the MSI.
Thank you in advance for any advice.
You don't want to install copies of the Intuit SDK DLLs. The merge modules you need are in the SDK, in path Program Files\Intuit\QBSDK\tools. In this directory you will find both stand-alone installation executables and merge modules. In the MergeModules directory, you will find merge modules for both QBFC and QBXMLRP2.
If you are using Visual Studio to create an MSI the best way to add the correct merge modules is to add the Intuit SDK MergeModules directory to the search path of your setup project. To do this, select the project in project explorer, then click the property pane or hit F4. This should bring you to the setup project properties where you should be able to see the SearchPath property.
Once you have added the MergeModules directory to SearchPath, you should see the merge modules added automatically in the Detected Dependencies folder of your setup project. You will see both the Intuit module (either QBFC or QBXMLRP2) and also the xerces parser merge module (the Xerces parser is used by the SDK).