Here's the code I used:
If MMC3 has a value, then it's installed.My snap in is optional, so I
just make it available or not, depending on MMC3 install state. If you
require it for your product, then you may be better served by having a
bootstrapper, or at least an instal
Alright, so if I understand things right, I need to capture the
registry entries created by installutil and write them into the Wix
file so that the Windows Installer writes them directly.
How about running mmcperf which is necessary to get the MMC 3.0 API
into the global assembly cache on XP and
You'll need to follow the manual registration process, and build the
registry entries yourself. There is no extension to handle this as-is. A
search on MSDN should get you the results you need, depending on the
platform you used to develop the snap in.
Heat may be able to harvest the registry in
My understanding from documentation on MSDN is that installutil
shouldn't be used to register the MMC 3.0 snap-in in actual
deployment. What then is the correct way to register an MMC snap-in
with a Windows Installer built with Wix? I'm currently using Wix 3.5
since that's what had the VS2010 integ
4 matches
Mail list logo
