MSI: Using regasm to register COM may cause resiliency during application launch

Building an installer for an application in VS2005. The application consists of several dll projects and merge modules with third party references. After the installer has been built and the application installed. Launching the application brings up a series of Windows Installer resiliency that continues for a long time before the application is finally launched….

0

Windows Installer 4.0 – MSI that installs data files under System Protected folders does not remove files upon uninstall.

Installing data files (.mdb) into System Protected folders (Program Files, System32 etc..) on Windows Vista machines as Standard user. Upon uninstall the data files appear to be removed, however when a new version of the application is installed the older data files are still referenced by the application.   Due to file virtualization on Vista,…

0

MSI: Unable to elevate an uninstallation via ARP in Vista

  MSI built using WiX Installer consists of Actions that require elevation.   The CustomActions are not designed to run under SystemContext. The installation/uninstallation will have to be done using an Admin command prompt. The uninstallation using Add/Remove Programs will not work due to it being not elevated.   WiX does not generate a bootrapper…

0

Native Custom action dll fails to build on x64

when you changed the build environment from Win32 to x64 and tried to build the setup project Its giving Error the Visual studio 2005 always complained the error message “Entry point ‘xxxxxx’ not found in module ‘xxxxxx’ for custom action ‘Primary Output from xxxx’ “ and stopped the building. -If you are using VS 2008….

0

Per-User installation of an MSI as standard user on Vista is installing files into Administrators profile

Files are being installed into the Administrators Profile rather than to the Standard Users profile.   This does not appear to be the default behavior for an Admin assisted installation as per documentation on http://msdn2.microsoft.com/en-us/bb384154.aspx   “Windows Vista built-in installer detection prompts for consent when you run under UAC. A bootstrapper (Setup.exe) built with Visual…

0

MSI: About the Uninstall Registry Key, WindowsInstaller Value

MSI packages built using Visual Studio Setup and Deployment project create the following registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\<Product Guid>\WindowsInstaller.   There is no official Microsoft documentation for this registry key but the result of changing its value are as follows :-   If the “WindowsInstaller” registry entry is “1”, the uninstall program set in the ProgramPath of…

1

How to make ClickOnce work over SSL requiring client certificates

Current feature limitations of Clickonce does not provide for security over internet by design.   It does work over SSL with server certificates which provides a mechanism to let users know that the application is coming from a trusted publisher. However, it you want to secure your application itself to a limited set of users…

1

How to build an MSI to deploy ActiveX control

1. Create a new Setup and Deployment Project in Visual Studio.   2. Include the ocx files in the Project using the “File System Editor” as in http://msdn2.microsoft.com/en-us/library/4ddxk2ye(VS.80).aspx It’s better to have the files in system32 folder.   3. Go to the launch conditions editor and create a new File search to search for the…

0

How to disable the default Launch condition for the .Net Framework in a Visual Studio Setup and Deployment project.

Two ways to do this.   1)Create a Transform to make apply changes to the MSI as to skip the default launch condition. You may then author a Custom launch condition to only display a message and exit the installation. Open the complied MSI using ORCA, click On the Transforms menu and select New Transform….

0