Showing results for February 2008 - Visual Studio Setup

Feb 19, 2008
0
0

Another Workaround to Add New Components to Existing Features

Heath Stewart
Heath Stewart

Yesterday I described an issue when adding new components to existing, not-installed (absent) features the feature tree is installed. This can lead to prompts for source or failed installations. One workaround is to add new, top-level hidden features. This works well unless new resources have a dependency on the older resources installed by the ...

InstallationLoggingWiX
Feb 18, 2008
0
0

Adding New Components to Existing Features Installs the Feature Tree

Heath Stewart
Heath Stewart

As Developer Division starts to ship patches for the Visual Studio 2008, some users are being prompted for installation source media. This is a resulting of Windows Installer needing the original source files if, for example, files are missing from disk when you repair your product or backup files are not available during patch install. If you are ...

InstallationVisual StudioLogging
Feb 12, 2008
0
0

Debugging Custom Actions: Leaked Handles

Heath Stewart
Heath Stewart

Debugging custom actions isn't exactly the easiest action to do; Windows Installer spawns separate processes - remoting servers - to run in-process custom actions. Any opportunity to diagnose issues without debugging can be helpful.For example, an issue that comes up from time to time is leaked handles. A Windows Installer debug log might show ...

InstallationLoggingCustom Actions
Feb 8, 2008
0
0

Get Binder Variables for Assemblies without Installing into the GAC

Heath Stewart
Heath Stewart

Binder variables in WiX are variables that are resolved, coincidentally, at bind time. This is when the linker, light.exe, collects file information, assigns auto-GUIDs, and generates the output packages among other things. There are binder variables for all versioned binaries, and binder variables specific to both managed and native assemblies or ...

InstallationWiX.NET