Video Screencast Help

Wise Packaging

Results for Wise Packaging

Merge modules provide a standard method by which developers deliver shared Windows Installer components and setup logic to their applications. Merge modules are used to deliver shared code, files, resources, registry entries, and setup logic to ...
Blog Entry by WiseUser | 01 Nov 2007 | 0 comments
A corrupt file will not trigger Windows Installer to perform a self-repair. This is because the Windows Installer checks only for file existence when checking a component that uses a file for its keypath. Read on to learn more. Although a corrupted ...
Blog Entry by WiseUser | 31 Oct 2007 | 0 comments
With Microsoft Windows Installer, an application's entry points play a major role in installing advertised features and initiating the self repair of an application. When a user uses an entry point to launch an .MSI-based application, Windows ...
Blog Entry by WiseUser | 31 Oct 2007 | 0 comments
A nested installation is a type of Custom Action that installs or removes another .msi package (sometimes called the child MSI) from within a running installation (called the parent MSI). Properties of Nested Installs Nested installations do ...
Article by R-Vijay | 30 Oct 2007 | 8 comments
Here are a couple of approaches that'll keep that pesky Windows Installer away from files you don't want uninstalled when an uninstall script is run. Hope you find this info useful. To modify the Component Table, follow these steps: ...
Blog Entry by WiseUser | 30 Oct 2007 | 5 comments
Here's some reference information about the registry hives. (I like to keep lists like this close, because I never know when I need them.) Hopefully this info will be as helpful to you as it has been to me. HKEY_CLASSES_ROOT - This branch ...
Article by WiseUser | 29 Oct 2007 | 5 comments
WiseCOMReg is a tool to find out the registry keys of individual components so that one can specifically remove these from the WSE or REG file which is included with Wise Installer. Further, this is a command-line tool and should probably be copied ...
Article by R-Vijay | 26 Oct 2007 | 0 comments
Bootstrapping is nothing but a process. Until the Windows Installer Service is pervasive, any software that depends on the Windows Installer being present must first ensure that the Installer is in fact present. Here's some background ...
Blog Entry by WiseUser | 26 Oct 2007 | 0 comments
This technique can be used when more than one version of a component needs to exist on a workstation and the two components are binary compatible. In this case, one of the components can be placed in the same directory as the application, and a file ...
Blog Entry by R-Vijay | 26 Oct 2007 | 0 comments
A Windows Installer Transform (.mst) contains a set of alterations to a Windows installer package (.msi). In order to correctly view the changes a transform makes, the .msi package that served as the 'original' should be used as the base ...
Blog Entry by WiseUser | 25 Oct 2007 | 4 comments