Separate Installs for Service and Desktop Application

The install originally lumped a Windows Service and a Desktop application together in one install.


This created a problem in the Install for Everyone. The Resilency was firing because of items in the Desktop application install. Specifically, Shortcuts installed per user were causing the Resilency install to fire when the second user logged in.

The Windows Service Installer does not handle this situation. And testing for the existence of the service causes a corrupt install state.

The less than ideal solution was to have separate installers for the two components.

Link: MSDN Windows Installer Deployment

MSDN: Windows Installer Deployment

RequiresElevation property

RequiresElevation property

Recently upgraded a 'vdproj' installation from 2005 to 2008 and encountered new 'RequiresElevation' property.

"MsiBootstrapper"
{
"LangId" = "3:1033"
"RequiresElevation" = "11:FALSE"
}