The ESRIRegasm utility being called generates a registration database (xml file) for a dll as well as calls RegAsm. It's required for extending the ArcGIS environment. Currently I have in place a system where the build msbuild script calls this utility so the xml files are generated. These files are then part of the installation. This works, but as soon as a public interface is changed in a dll I need to remember to manually run heat and update the installer. Adding or removing dlls also means adding or removing the corresponding xml file to the installer.
Running the ESRIRegasm utility on the dlls after installation takes care of all registration, the installer doesn't need to know about the xml files or about COM registration of the dlls, and the only time I need to revisit the installer is when I want to add or remove a dll. This is what I want to accomplish, and it works as long as I don't have too many dlls to fill up the available sequence numbers after MsiUnpublishAssemblies. But I do... /Asker -----Original Message----- From: David Watson [mailto:dwat...@sdl.com] Sent: den 6 april 2011 11:30 To: WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Too many CA:s (LGTH0179) What is special about your registration that means you can't just heat them, your code implies it's just regasm? -----Original Message----- From: Asker Brodersen [mailto:asker.broder...@esri.se] Sent: 06 April 2011 06:41 To: WiX-users@lists.sourceforge.net Subject: [WiX-users] Too many CA:s (LGTH0179) Hi, During installation/uninstallation we need a special registration of our dll:s. This lead to four CA:s being scheduled for each dll: <InstallExecuteSequence> <Custom Action ="InvokeESRIRegAsm_Cmd_Meldis.Search.dll" After="StartServices">$Meldis.Search.dll>2</Custom> <Custom Action ="InvokeESRIRegAsm_Meldis.Search.dll" After="InvokeESRIRegAsm_Cmd_Meldis.Search.dll">$Meldis.Search.dll>2</Custo m> <Custom Action ="InvokeESRIRegAsm_CmdUninstall_Meldis.Search.dll" After="MsiUnpublishAssemblies">$Meldis.Search.dll=2</Custom> <Custom Action ="InvokeESRIRegAsm_Uninstall_Meldis.Search.dll" After="InvokeESRIRegAsm_CmdUninstall_Meldis.Search.dll">$Meldis.Search.dll=2< /Custom> </InstallExecuteSequence> But as I have close to a hundred dll:s, this results in the LGHT0179 error for MsiUnpublishAssemblies, I presume there simply isn't room in the sequence table for all of them. How do I work around this problem? Thanks, Asker ----------------------------------------------------------------------------- - Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
