Re: [WiX-users] any insights as to why sql extension commands containing public property references are not working

Ok. I just submitted the following wix feature request which hopefully outlines clearly what we are seeing and what we would prefer to see. https://sourceforge.net/tracker/index.php?func=detailaid=2655321group_id=105970atid=642717 Subject = support defining multiple sql:String sequence

Re: [WiX-users] any insights as to why sql extension commands containing public property references are not working

What you are seeing is a limitation in the code. I'm not sure that there is a real requirement behind the limitation but the code does expect things to behave the way you list. If you think it should be different, feel free to file a feature request with a clear statement of what you see and

Re: [WiX-users] any insights as to why sql extension commands containing public property references are not working

I agree getting the exec wrapped statements correct, required so we could incorporate use of installer public properties in the sql statements, required a couple of passes. What we've found in testing of this build output is that everything worked once I limited the sql:String statements to

[WiX-users] any insights as to why sql extension commands containing public property references are not working

Any insights as to why the following sql extensions commands that create a sql login and db user setting work Property Id=DATABASESHOST Value=localhost sql:SqlDatabase Id=MasterDatabase Database=master Server=[DATABASESHOST] / sql:SqlDatabase Id=Database1 Database=MyDeliverableDatabase

Re: [WiX-users] any insights as to why sql extension commands containing public property references are not working

p.s. looking at my verbose logs searching for ExecuteSqlStrings hits I only see RollbackExecuteSqlStrings hits containing both the sql login and db user settings I want applied during install ( and during component uninstall rollbacks) as well as the settings I want applied during uninstall (

Re: [WiX-users] any insights as to why sql extension commands containing public property references are not working

p.s. looking at my verbose logs searching for ExecuteSqlStrings hits I only see RollbackExecuteSqlStrings hits containing both the sql login and db user settings I want applied during install ( and during component uninstall rollbacks) as well as the settings I want applied during uninstall (

Re: [WiX-users] any insights as to why sql extension commands containing public property references are not working

Robert, Just one observation, are you sure that the difference in between using create (in the exampel that works) and wrapping the create inside an exec command (in the example that fails) is not the problem. Both look okay to me, but I have had fun in the past with getting exec('strings') to