Thank you for you help. I actually got it working by running tallow -c on the .dll and then added that to my .wxs file. This registered my .dll just as I wanted.... Mike
Pally Sandher wrote: > > If you use a CustomAction to register the DLL on install you also need > to provide a CustomAction to unregister on uninstall & on > rollback/failed install. Hence it's not recommended especially when > you're trying to do something which is eminently possible using the WiX > schema & tools anyway. > > As you state in your previous e-mail use tallow.exe (or heat.exe in 3.0) > to extract the registration information from the DLL. You need to use > the -s option in tallow e.g tallow.exe -s mydll.dll > This will output the registration information in XML format for you to > merge into your code where required (I would pipe it to a file rather > than try to copy & paste from a command prompt). You will want to change > any paths the generated XML has in it so they are correct when installed > e.g. it may have C:\Program Files\myapp\mydll.dll which you probably > want to replace with something like [TARGETDIR]mydll.dll. Other than > that it should be fine but with all code, testing is the key. > > The other option is to use the SelfRegCost option on mydll.dll entry in > your XML. This sets the Self Register flag in your MSI for this file & > leaves it up to the MSI to handle the registration. I'm not sure how > clean this is at uninstall & rollback though, I guess it depends on the > DLLRegisterServer code in your DLL hence again it's not recommended > AFAIK. > > Good luck =) > > > > <http://www.iesve.com/> > > Palbinder Sandher > Software Deployment and > IT Administrator > > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > http://www.iesve.com <http://www.iesve.com/> > > **Design, Simulate + Innovate with the <Virtual Environment>** > > Integrated Environmental Solutions Limited. Registered in Scotland No. > SC151456 > Registered Office - Helix Building, West Of Scotland Science Park, > Glasgow G20 0SP > > Email Disclaimer <http://www.iesve.com/disclaimer.html> > > > > > > > > > > > > > > > > > -----Original Message----- > From: [EMAIL PROTECTED] [ > mailto:[EMAIL PROTECTED] On Behalf Of > mike.tihonchik > Sent: 09 April 2008 16:30 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] re gistering .dll in WiX with CustomAction > > > Ok, I have read that almost everybody suggest not to use the > CustomAction to register .dll My question is though, the .dll I want to > use, is used only by this one piece of code, and if its get removed it > would not affect any other piece. Is CustomActions still a bad choice to > do it???? Thanks in advance, MIKE > -- > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://www.nabble.com/registering-.dll-in-WiX-with-CustomAction-tp16587201p16609074.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
