> I'm trying to package a legacy program that registers some third-party
> ocx and dlls. I see that the consensus is that I should be handling > this with a registry component. However, this application's > 'installer' just copies stuff into a folder off the root of c:\ and > runs a 'register.bat' to > regsvr32 /s each necessary item. > > In this case, is there really any downside to making the files > self-register? For me the real problems with self-registration came when my components had dependencies on C++ runtimes, that were not available at the point at which I was trying to run the self-registration. Regards, John ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
