I know this has ben discussed here before, however, that case was somewhat different from what I'm about to describe.
I have created a merge module for a database application that delivers an "add-on" module for the base application (contained in the base install). In the base installation, I collect information necessary to form a connection string, and use the connection string in the base install to execute SQL scripts. I am aware that I can directly execute SQL in the install, and I use that functionality, however, I must run some executables (as custom actions) and then a second set of SQL Scripts to initialize my database. The merge module must also execute SQL Scripts to initialize it's functionality in the database.
As a result of this, I would like to pass the connection string (and a couple other pieces of information) to the Merge module. I have tried this a a configurable parameter tied to a User-defined property in the base installation, however, all I seem to get is the Property Name in the merge module. The previous thread here implies that FORMATTED properties can be passed as parameters, but other references seem top contradict this, stating that parameters will always be unformatted due to the interface.
So to restate; what I want to do is a pass a User-defined Property from the base application to a merge module. I would like to loosely couple the merge module, and prefer not to use a reference to the MM property with the MM GUID appended. I have thought of using a file to pass the data from the base install to the merge module, but do not want to do this as there may be password data in the connection string, etc.
Is there a means of passing Property *data* from the base install to the merge module? I would think that I could specify a Property at design time that would pass the DATA at runtime. Am I missing something here?
FOLLOW US
Get the latest news in Application Packaging