Hi Mike, Thanks for the response - it was the one which is feared i might get.
The article was quite interesting. I must admit that I agree with the MSI team that Custom Actions should be kept to a minimum, however I do not buy their justifications. On the technical problem of two framework versions in the same process, this is a only a real problem (IMHO) if you are using third party merge modules. In my opinion they should allow managed custom actions and create a new ICE for checking they all require the same framework version. On the strategic front, with the MS platforms becoming more and more sophisticated and integrated the need for custom actions is always going to exist to some extent. The main problem with adding code to the application to perform steps which a custom action might undertake (something which is suggested) seems to me to come during uninstall. For example, if you had an application which changed something in the 'system state' on first run, how would this be undone during uninstall? I agree that it would be good for these custom actions to be developed by the same group which creates a component, however without someone driving that at MS (and I don't get the impression that there is), that is never going to happen. Furthermore, the long term MS strategy is more and more towards .net, so adding better support to MSI for deploying these applications would seem to me to be imperative. I am not going to bother raising a bug against the VS team - we have raised a few which are more serious than this but nothing is planned to be done about them. If they are not going to support it, i think they should release the source. Anyway, just thought i would get that off my chest :) - time to crack out VC++ (which will be good for me anyway as i have not done much native development work in the last 12 months) or find a cunning way to perform the install without the need for custom actions. Thanks again. Rick Hobbs Neoworks Ltd. Mike Dimmick-2 wrote: > > You're awash in a sea of unsupported. > > InstallUtilLib is an *undocumented* helper library shipped by Visual > Studio. > Pretty much all you can do is file a bug against Visual Studio (which will > of course suffer from exactly the same problem). > > Officially managed custom actions are not supported: > http://robmensching.com/blog/archive/2007/04/19/Managed-Code-CustomActions-n > o-support-on-the-way-and-heres.aspx. > > The answer I'm afraid is to move whatever custom action is necessary into > the application code, or rewrite your custom action in unmanaged C++. > > -- > Mike Dimmick > > -- View this message in context: http://www.nabble.com/Vista-Verification-Test-Case-23---Custom-Actions-using-InstallUtilLib-tp14689342p14730542.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
