Burn in the corporate environment.

A good question about Burn was raised in the comments on my blog entry about Burn yesterday. The tiny executable that downloads the bulk of the installation content is great when you want to install on your computer. However, if you need to distribute the installation to many machines, like most corporations do, downloading from the Internet is more expensive than downloading from a corporate server. Fortunately, we have a solution for this scenario.

Burn will only download files from the Internet that it cannot find locally. That means you can download the files once and copy them to a network share or burn to CD/DVD (if you prefer sneaker net) for sharing in your corporate environment. The only tricky part is figuring out what files go where. Enter the "-layout" switch.

The "-layout" switch instructs Burn to download the installation content and create a complete directory layout. That layout will ensure Burn won't need to access the Internet later. Unfortunately, as you can see in SFBUG:3011150, the "-layout" switch isn't implemented yet. This is a good example of one of those smaller things we'll be addressing after the large work items are completed this month.

It's clear there is a lot of excitement around Burn so keep the feedback flowing and I'll keep the code coming.

 

4 Comments

Comment by Marais on Tuesday, September 07, 2010 11:37 PM

Rob,

Maybe I don't understand Brun yet, but why not just supply an option where the file won't be downloaded from another location at all but rather be packaged into one package? Yes, this would make the installer alot bigger than the 130 odd KB that you mentioned, but sometimes the size of the setup package isn't really an issue since it is only 5 or 6 MB.

Comment by Neil Sleightholm on Wednesday, September 08, 2010 8:16 AM

Rob, in all the environments I need to support then Internet access cannot be relied upon. This isn't just corporate. Can I just comment that I think downloading components as part of the install is not a good way to build releases in most cases. I know microsoft does it but I never pick that option and go for the full download as I am bound to need to install a second time. May be it is a difference in Internet speeds, here in the uk a lot of people still have slow connections, 1mb/s is not uncommon.

Comment by David Marks on Tuesday, September 14, 2010 11:32 AM

I second Neil's comment ... and here's a corporate scenario in the US of A [and quite a few other places, too]: Hospitals.

I don't know of any hospital / healthcare org that permits unrestricted internet access.

Comment by Christopher Painter on Saturday, September 18, 2010 12:09 PM

One of the great things about MSI is to be able to see and transform the MSI. Sadly you typically lose this when you shove it inside of a setup.exe.

One of the design goals that I hope burn ( or any other bootstrapper ) has is to extend this to the bootstrapper itself.

I would hope to be able to extract / decompile the boootstrapper, add/remove packages, change download locations, create and embed new transforms for the msi and what not on then rebuild it back into a compressed format.

I also hope to be able to take an existing MSI off the shelf ( perhaps not even a WiX MSI ) and build a new bootstrapper around it without having to build the MSI in WiX.

Any chance Burn will be able to do these things?

Leave a comment
optional