InstallAware Windows Installer Partial Web Deployment

InstallAware introduces a novel partial web deployment technology that solves these problems:

The source files of a setup can be placed on, and read from, various locations:
- The main setup.exe file itself
- Physical media, such as a CD or DVD disc
- A corporate file server
- An Internet file server
- A decentralized Torrent file
- A decentralized Magnet link
None of the above locations are encumbered by artificial limitations - regular file servers, HTTP, FTP servers all work just fine.
When a setup is running, it will attempt to access the source locations only if necessary - for instance, when the associated application feature has been selected by the user, or if an application runtime is not found on the target system.
The main setup.exe file can contain essential application files and runtimes which are always required - so the setup.exe works without forcing an Internet connection unless absolutely necessary. You are not constrained to deliver empty setup.exe files which don't work without an Internet connection.
Application runtimes and other rarely used features can be stowed away in web locations, to be downloaded on-the-fly when needed. This trims the fat off of the main setup.exe, while still assuring it works independently. Moreover, if a download is interrupted, the setup engine can resume exactly where it left off. Downloads also transparently detect proxy server information.
Setups may share the same source locations. For instance, if two applications require the .NET Framework, they can both read the framework from a single source location, preventing the need to replicate source files and downloads for each setup.

InstallAware calls each source location a web media block. Web media blocks are the core of partial web deployment technology and make all of the above possible.

What is a web media block?

A web media block is any part of your setup that installs files. For example, you could have two media blocks - one that installs your main application, and another that installs your help files. You can splice your setup into as many web media blocks as you like in your setup script.

How does a web media block work?

When setup determines that a particular file inside a media block will be installed, it downloads that block from the exact URL you place it on the web. Only web media blocks that are required for installation are downloaded. Building on the above example, if the user chose to install the main application, but not its help files, only the main application files would be downloaded. The help files would not be downloaded.

How are web media blocks useful?

They help save bandwidth - both on your servers and on your users side. Your users download only the portions they need. You don't bloat your setup with redundant data.

Isn't this web deploy?

No. Unlike most web deployment schemes, web media blocks are free of constraints. Each web media block is contained in a single file, which you may freely deploy at any URL. You may also precisely define which files in your setup belong to which media blocks. Moreover, with traditional web deployment, you either deploy your entire setup online, or have to keep it all offline. With web media blocks, you can precisely control what parts of your setup go where.

Can web and offline content be mixed?

Yes. Using web media blocks, you may even designate parts of your setup "offline". Offline content will be included in your main setup file, therefore each user that downloads your main setup program will already have that content without having to download it from the web. This is useful when parts of your setup are always required.

Can common runtimes be installed in this way?

Absolutely. In fact, this is one of the best ways to use web media blocks. If your application requires runtimes that may already be present on the end users system, simply place them inside a web media block. This way, your setups will download the required runtimes only if they are not already present on the target system.

What about resuming interrupted downloads?

To ensure the most positive user experience, when downloads are interrupted, InstallAware automatically resumes downloading them after a short idle period. This guarantees that when you walk away for "lunch", a momentary lapse in your Internet connectivity doesn't stall the application you are installing for hours - everything will be ready when you're "back at your desk", no matter how many interruptions in the meanwhile.

What about security?

Each web media block file is code signed, and at runtime, the actual name of the signing entity is verified against the expected signer. This helps eliminate a new attack form, where third parties obtain legitimate code signing certificates and re-sign tampered files with their unrelated but legitimate third party certificate - thus bypassing signature checks which don't also take the extra step of verifying the name of the actually expected signing entity.

How about redundancy?

You may specify multiple redundant sources for each of your web media block files. The installation engine will skip to the next redundant source when a source it attempts to download fails, or fails code signing verification, or has other issues.