bootstrapper

I am migrating from IIS WebAPI to OwinHost. Utilizing the latest pre-release versions of nuget packages, I successfully used instructions here: https://github.com/ninject/Ninject.Web.Common/wiki/Setting-up-a-OWIN-WebApi-application Here is stub of my code: public void Configuration(IAppBuilder app) { var config = new HttpConfiguration(); config.MapHttpAttributeRoutes(); app.UseNinjectMiddleware(CreateKernel); app.UseNinjectWebApi(config); } private static StandardKernel CreateKernel() { var kernel = new StandardKernel(); kernel.Load(Assembly.GetExecutingAssembly()); RegisterServices(kernel);

I want to enable Upgrade in the 2nd version of our WiX custom BA installer. In my Product.wxs, Product ID is set to *, version is set to 2.0.0, and upgrade code remains the same as the 1st version's. To detect Upgrade, I used DetectRelatedBundle event handler in the Boostrapper. The MajorUpgrade tag in the MSI looks like this: <MajorUpgrade AllowDowngrades="no" DowngradeErrorMessage="A newer version of [ProductName] is already installed." AllowSameVersionUpgrades="no" Schedule="afterInstallInitialize" /> In my installer UI, I have an Install button. When this button is clicked during Upgrade

I'm using InstallShield 2013 LE and I'm looking to do something similar to SQL CE 4.0 as a InstallShield Prerequisite . Only, I want to install .Net Framework 4.5, if it's not already on the machine. I have the file I need for the framework, but LE doesn't allow me to work on prerequisites. I saw the recommendation for DotNetInstaller and I downloaded and started working on that. But it looks like DotNetInstaller is very old and doesn't include .Net Framework 4.5 (stand-alone) in its list. Is there a way to add it? Then I looked at WiX and wasn't sure I could follow the documentation. I also

I have a bootstrapper that installs a MSI-package. How can i achieve that at least the msi-package-installation gets logged( verbose logging )? And where can i set the log-file-path? Because I won't be able to log everything i guess? And no, i don't want a cmd-solution , i need to implement this into my setup Found LogPathVariable, but don't really know how it works? <MsiPackage SourceFile="$(var.Setup.TargetPath)" LogPathVariable="" /> Googled arround many times and havn't found a solution for this problem, any help? The default case (no LogPathVariable set) will create logs in C:\Users

We've decided to create a custom bootstrapper for our deployment solution. We are currently re-writing and re-designing our deployment strategy for all of our products. Sadly, none of us are deployment experts. Here's what we have so far: A. The MSI packages will be authored in InstallShield. We will use whatever feature Installshield offers (IIS integration, COM registration, Registry, etc). The dialog's created by InstallShield will not be used (that is what the bootstrapper is for). The MSIs will be installed silently. B. Whenever we need to write CA's for stuff that InstallShield can't