Hi, I am maintaining the installer for our main product. This product is extensible and I was wondering how I would go about making installers for our extensions?
What I would like is for the extension installers to refuse being installed if the main application isn't installed. Furthermore I would like the extension installers to be removed if the main application is removed, but NOT if it is being upgraded. Currently I am not using patching or minor upgrades, only major upgrades for our main product. What we do today is essentially copying the extension assemblies into the folder of the main application, and then it automatically detects the new extensions and loads them (after a restart). Sometimes we need to tweak or change some settings which we then do either by hand, or by a small application designed to handle the specific settings. I would really like a general scheme for deployment extensions, but my knowledge and understanding of WiX and MSI is not so complete that I can think my way through the problem on my own. So I turn to you for some tips, guidelines and suggestions? I am happy to provide more information should it be needed. /Thomas Due ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
