OK, I am redoing some of my installations to be in merge modules. Now, I have no idea what I'm doing, so it's kind of learn as I go. I'm stuck in a few spots, and was hoping someone out here would be kind enough to help me. :-)
I am installing a .NET web application, which is why this gets complicated. * I have all the files to install. This was pretty straightforward. * I have some config changes to apply. I had this working in the .msi, but does the module have access to the public properties the containing MSI will have? Is this the preferred method of getting data, or is there some mechanism for explicitly passing the information? (something like CustomActionData for CAs) * I need to set up IIS properly. This gets complicated since I want to allow a choice for a web site, or a virtual directory installation. Also, different versions of IIS are configured differently. I don't mind having a complicated set of conditions in my MSM, I just want to avoid making an MSM for each of these conditions. Is this possible? * I am using the ASP.NET built in Membership providers, so I need to either run aspnet_config.exe, or directly run the SQL script against the datasource. Is it possible to test for the existence of this database before running either of these? Thanks in advance for any assistance... I'll take help for any or all of these questions. :-) Chris ------------------------------------------------------------------------- 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
