What is the difference between customizing an installation through the use of command-line parameters and the application of transforms? Get your answers (right here) while they're hot.
As a matter of best practices, we have a standard way to increment version numbers and codes based on the extent of the upgrade. I thought this might be useful to others in the community who are faced with similar challanges. As always, these worked for us but your mileage may vary.
Here's a quick step-by-step that walks you through the process necessary to set up your packaging system so it creates packages (all packages) with elevated privileges.
MSIZAP: A cool little utility that removes the MSI meta data from your computer. Us it when (for some reason) uninstall is broken and won't freakin' do it's job ... uninstall.
Here are a few questions (and their answers) about some obvious and some obscure Wise Package Studio functionality -- just to make sure you're keeping up with your homework. There will be a test at the end of the semester so read up ;)
Source Resiliency: Applications that rely on network resources for installation-on-demand are susceptible to source failures if the source location should change for any reason or become damaged.
A number of MSIExec processes can be running during an installation. The reason for this is that Windows Installer uses a client-server model for performing installations. Additionally for security reasons, Windows Installer hosts DLL and script custom actions in a "sandbox" process.
