Where are the Bootstrapper packages installed?

QuestionHow can I programatically determine where the Bootstrapper packages are located?    Answer If you would like to know how to programatically locate the Bootstrapper package location (if you were developing an installer for your custom package for example).  Check the following registry key: HKLM\Software\Microsoft\.NetFramework\sdkInstallRootv2.0 Then append the string: “Bootstrapper\Packages\”

0

Can the Bootstrapper do complex logic for install conditions?

QuestionCan the Bootstrapper do complex logic on the install conditions?  Such as FailIf (X = true AND Y = false) AnswerNo.  The Bootstrapper only executes a single install condition at a time.  If you need more complicated logic then you will need to expand it out into multiple Command statements and use BypassIfs.  For example,…

0

Changing package deployment method post build

QuestionIs there a way I can change the Bootstrapper after setup.exe has been built? AnswerYes, you can.  Although you can’t change the packages or logic of the Bootstrapper you can change the way packages are deployed. You can use the command line to either turn HomeSite on/off or set the Components and Prerequisites URLs.  For…

0

Using the Bootstrapper to wrap a Windows Installer package

This article is to serve as a tutorial for converting a standard Windows Installer package (*.MSI) into a Visual Studio 2005 Generic Bootstrapper package. Doing so will allow you to wrap a program prerequisite in a Bootstrapper package, to allow its deployment alongside any ClickOnce deployment or Setup Project. First Step: Directory Structure & File…

0

Localizing Bootstrapper Packages

Localizing software has traditionally been difficult process; fortunately however localizing your Bootstrapper package doesn’t have to be. If you use separate localization-specific functionality from functionality required for all packages, the localization process is quite simple. Package vs. Product XML manifest The key to understanding the Bootstrapper package localization process is understanding the difference between the…

1

Deploying the .NET Framework version 1.1

QuestionCan I use the Visual Studio 2005 Bootstrapper to deploy the .NET Frameworks 1.1?  Do I need to purchase Visual Studio 2005 to do so? AnswerYes, there are two options for creating a Bootstrapper for the .NET Framework v1.1.  The first is to download a Bootstrapper manifest for the Visual Studio 2005 Bootstrapper.  Additional manifest…

0

Using the Bootstrapper to launch an EXE

QuestionIs there any way I can have my Bootstrapper launch an EXE or file other than my .application / .msi? AnswerUnfortunately the only way to have a Bootstrapper launch an EXE file is to use MSBuild to create setup.exe from the command line. This isn’t too difficult, but you will need to hand-author an MSBuild…

0

Bootstrapper – Security

In this article we will discuss security in the Bootstrapper.  Although setup.exe provides a great service of installing program prerequisites, how do you know you can trust it?  What if hackers attack a web server hosting redistributable packages?  Would every deployment then grab and install those compromised bits? Rest assured that the Bootstrapper makes your installation…

1