date:20090224


Hi,

I have a registry key that is of type binary and has is a long series of
numbers.  When I export it from regedit, it looks like this:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FooBar\Security]
Security=hex:01,00,14,80,90,...

I'm having trouble expressing this inside the RegistryKey as:

RegistryValue Type=binary Name=Security Value=01,00,... /

But I keep getting the error:

error LGHT0204 : ICE70: The value '#x01,00' is an invalid hexadecimal value
for registry entry reg001E0C73C604AACC31F75D0

How do I express this correctly?

Thanks,

Roy
-- 
View this message in context: 
http://n2.nabble.com/Writing-a-Value-for-RegistryValue-element-of-Type-Binary-tp2378965p2378965.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Updating program from InstallShield Setup with .msi setup fails

Sebastian Klemm wrote:
 The two Setups have the same Upgrade Code, the WiX Setup has a higher Version 
 number. 
   

Well, error code -2147287038 is ERROR_FILE_NOT_FOUND, so does 
C:\Windows\Installer\908c3.mst exist? Can you reproduce the problem with 
a fresh install of the old product? You can use the IgnoreRemoveFailure 
attribute to let the upgrade go through anyway.

-- 
sig://boB
http://joyofsetup.com/



--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Date calculations

2009-02-24 Thread Reddy, Mallikarjun (GWM-CAI)

Hello, 

In a custom action, I am going to run an exe with args. One of the args
is a date that is 30 days older than today. Could some let me know how
this could be done? 

Here is how I am trying to solve this.

Create a property calle OLDDATE
Create a custom action that has vbscript which runs before the above the
exe's custom action. 
My VBScript custom action looks like this. This is throwing an error. I
tried without set. No luck. Any way of fixing this and any other smart
of doing this ? Thanks in Advance 

CustomAction Id=CalcOldDate Script=vbscript
  SUB CalcMigratorDate()  
   set Session.Property(OLDDATE) = DateAdd(d,-30,DateValue(Now))
  End SUB
  call CalcMigratorDate
/CustomAction

--
This message w/attachments (message) may be privileged, confidential or 
proprietary, and if you are not an intended recipient, please notify the 
sender, do not use or share it and delete it. Unless specifically indicated, 
this message is not an offer to sell or a solicitation of any investment 
products or other financial product or service, an official confirmation of any 
transaction, or an official statement of Merrill Lynch. Subject to applicable 
law, Merrill Lynch may monitor, review and retain e-communications (EC) 
traveling through its networks/systems. The laws of the country of each 
sender/recipient may impact the handling of EC, and EC may be archived, 
supervised and produced in countries other than the country in which you are 
located. This message cannot be guaranteed to be secure or error-free. 
References to Merrill Lynch are references to any company in the Merrill 
Lynch  Co., Inc. group of companies, which are wholly-owned by Bank of America 
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
Government Agency. Attachments that are part of this E-communication may have 
additional important disclosures and disclaimers, which you should read. This 
message is subject to terms available at the following link: 
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you 
consent to the foregoing.
--
 

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem with deferred Custom Action

Jacob, Christian wrote:
 After some research I found out that the user who calls LoadUserProfile needs 
 the SeTcbName privilege (Act as part of the Operating System). However, since 
 the custom action is run deferred in System context, I thought, it already 
 HAS all necessary privileges. 

Not necessarily. MSI gives up some privileges on Windows Vista and 
later. From 
http://blogs.msdn.com/windows_installer_team/archive/2006/10/30/preview-of-upcoming-kb-articles-windows-installer-4-0-on-windows-vista.aspx:

*KB Title:* Windows Installer (MSI) packages only have access to the 
specific privileges of the Windows Installer service on Windows Vista.

*Summary:* Software developers should be aware that, starting with 
Windows Vista, the Windows Installer service only has privileges 
required for software installation. Custom actions that require 
additional privileges will fail.

*More Information:* The Windows Installer service has the following 
specific privileges: 
SeTcbPrivilege,SeCreatePagefilePrivilege,SeLockMemoryPrivilege,SeIncreaseBasePriorityPrivilege,SeCreatePermanentPrivilege,SeAuditPrivilege,SeSecurityPrivilege,SeChangeNotifyPrivilege,SeProfileSingleProcessPrivilege,SeImpersonatePrivilege,SeCreateGlobalPrivilege,SeAssignPrimaryTokenPrivilege,SeRestorePrivilege,SeIncreaseQuotaPrivilege,SeShutdownPrivilege,SeTakeOwnershipPrivilege,SeLoadDriverPrivilege.
 
Since Custom Actions inherit the same privileges of the Windows 
Installer service, custom actions will have only these privileges, even 
when running in an elevated context. If your application installation 
requires configuration that requires other privileges, it can not be 
done though a Custom Action.


-- 
sig://boB
http://joyofsetup.com/

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

Roy Abou Assaly wrote:
 RegistryValue Type=binary Name=Security Value=01,00,... /

 But I keep getting the error:

 error LGHT0204 : ICE70: The value '#x01,00' is an invalid hexadecimal value
 for registry entry reg001E0C73C604AACC31F75D0

 How do I express this correctly?
   

The MSI doc doesn't say. I'd try removing the commas.

-- 
sig://boB
http://joyofsetup.com/


--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary


On Tue, Feb 24, 2009 at 1:46 PM, Bob Arnson-6 (via Nabble) 
ml-user+58260-683222...@n2.nabble.comml-user%2b58260-683222...@n2.nabble.com
 wrote:

 Roy Abou Assaly wrote:
  RegistryValue Type=binary Name=Security Value=01,00,... /
 
  But I keep getting the error:
 
  error LGHT0204 : ICE70: The value '#x01,00' is an invalid hexadecimal
 value
  for registry entry reg001E0C73C604AACC31F75D0
 
  How do I express this correctly?
 

 The MSI doc doesn't say. I'd try removing the commas.

 Value=00 01 gives:
error LGHT0204 : ICE70: The value '#x01 02' is an invalid hexadecimal value
for registry entry regA16537AC885C7B5BB23019846BB931C1.
Value=00;01 gives:
error LGHT0204 :ICE70: The value '#x01;02' is an invalid hexadecimal value
for registry entry regA16537AC885C7B5BB23019846BB931C1.
Value={01 02}
error LGHT0204 : ICE70: The value '#x{01 02}' is an invalid hexadecimal
value for registry entry regA16537AC885C7B5BB23019846BB931C1.

Hmmm...any other suggestions?  If regedit expects a comma, is there some
character replacement for it that WiX would want?

-- 
View this message in context: 
http://n2.nabble.com/Writing-a-Value-for-RegistryValue-element-of-Type-Binary-tp2378965p2379698.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem with deferred Custom Action

2009-02-24 Thread Jacob, Christian

I found out that when setting the InScript execution type of the managed CA 
from Deferred in System Context to Deferred Terminal Server Aware, then it 
works.

Jacob, Christian wrote:
 After some research I found out that the user who calls LoadUserProfile needs 
 the SeTcbName privilege (Act as part of the Operating System). However, since 
 the custom action is run deferred in System context, I thought, it already 
 HAS all necessary privileges. 

Not necessarily. MSI gives up some privileges on Windows Vista and 
later. From 
http://blogs.msdn.com/windows_installer_team/archive/2006/10/30/preview-of-upcoming-kb-articles-windows-installer-4-0-on-windows-vista.aspx:

*KB Title:* Windows Installer (MSI) packages only have access to the 
specific privileges of the Windows Installer service on Windows Vista.

*Summary:* Software developers should be aware that, starting with 
Windows Vista, the Windows Installer service only has privileges 
required for software installation. Custom actions that require 
additional privileges will fail.

*More Information:* The Windows Installer service has the following 
specific privileges: 
SeTcbPrivilege,SeCreatePagefilePrivilege,SeLockMemoryPrivilege,SeIncreaseBasePriorityPrivilege,SeCreatePermanentPrivilege,SeAuditPrivilege,SeSecurityPrivilege,SeChangeNotifyPrivilege,SeProfileSingleProcessPrivilege,SeImpersonatePrivilege,SeCreateGlobalPrivilege,SeAssignPrimaryTokenPrivilege,SeRestorePrivilege,SeIncreaseQuotaPrivilege,SeShutdownPrivilege,SeTakeOwnershipPrivilege,SeLoadDriverPrivilege.
 
Since Custom Actions inherit the same privileges of the Windows 
Installer service, custom actions will have only these privileges, even 
when running in an elevated context. If your application installation 
requires configuration that requires other privileges, it can not be 
done though a Custom Action.

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

Roy Abou Assaly wrote:
 Value=00 01 gives:
 
 error LGHT0204 : ICE70: The value '#x01 02' is an invalid hexadecimal value
 for registry entry regA16537AC885C7B5BB23019846BB931C1.
 Value=00;01 gives:
 error LGHT0204 :ICE70: The value '#x01;02' is an invalid hexadecimal value
 for registry entry regA16537AC885C7B5BB23019846BB931C1.
 Value={01 02}
 error LGHT0204 : ICE70: The value '#x{01 02}' is an invalid hexadecimal
 value for registry entry regA16537AC885C7B5BB23019846BB931C1.

 Hmmm...any other suggestions?  If regedit expects a comma, is there some
 character replacement for it that WiX would want?
   

WiX isn't complaining; the ICE validators are. Did you try no delimiters 
at all? (RegEdit isn't authoritative.)

-- 
sig://boB
http://joyofsetup.com/

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Can I prevent shut down of SQL Server service during uninstall on Windows 2008 Server?

2009-02-24 Thread Swandog

Hi:

I have an installer (built with WIX v. 2.0.2912.0) that has been working on
Windows 2003 Server, but on Windows 2008 Server it fails during uninstall. The
point where it fails is when it tries to connect to SQL Server. The error is
SQL Server does not exist or access denied.

What happens is the SQL Server service gets shut down, so the attempt to
connect fails. I watched services manager during an uninstall, and it shows
SQL Server service shutting down sometime before the uninstall gets to the
point where it needs to connect to SQL Server.

I don't see anything that should cause this service to stop - there is a
StopServices action in InstallExecuteSequence, but in ServiceControl table
there is only the service we install and MSMQServiceControl.

In our environment we use CAs to work with the database, including installing
and uninstalling. Here's an excerpt from the verbose log, showing the failure
coming from InstallFinalize, immediately after the call to the CA:

MSI (s) (3C:60) [14:18:06:731]: Executing op: ActionStart(Name=ATDropDB,,)
Action 14:18:06: ATDropDB.
MSI (s) (3C:60) [14:18:06:731]: Executing op:
CustomActionSchedule(Action=ATDropDB,ActionType=9222,Source=Function
CheckForNgDiagDB_Status()

...(a few lines of CA source code)
Action ended 14:18:38: InstallFinalize. Return value 3.

Is there a behavior change with Windows Server 2008 that breaks this, and if so
what is the correct approach to working with a database during uninstall?
Otherwise, what do I do to prevent the service from shutting down? If I can't
prevent it from shutting down, what about adding a new CA to start it up after
the point in the InstallExecuteSequence where it is automatically stopped?

Thanks,

Greg

_
Windows Live™ Hotmail®…more than just e-mail.
http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_howitworks_022009
--
View this message in context:
http://n2.nabble.com/Can-I-prevent-shut-down-of-SQL-Server-service-during-uninstall-on-Windows-2008-Server--tp2379802p2379802.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Date calculations

2009-02-24 Thread John Nannenga

DateAdd returns a date, Session.Property must take a string, hence the type 
mismatch error you were likely receiving.

Try this instead... Use FormatDateTime to convert your date object...

CustomAction Id=CalcOldDate Script=vbscript
  SUB CalcMigratorDate
  Session.Property(OLDDATE) = 
FormatDateTime(DateAdd(d,-30,DateValue(Now)))
  End SUB
  call CalcMigratorDate
/CustomAction


Standard disclaimer regarding script CAs goes here, though I didn't realize 
WiX made them so darn easy to add/use!/


-Original Message-
From: Reddy, Mallikarjun (GWM-CAI) [mailto:mallikarjun_re...@ml.com] 
Sent: Tuesday, February 24, 2009 12:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Date calculations

Hello, 

In a custom action, I am going to run an exe with args. One of the args
is a date that is 30 days older than today. Could some let me know how
this could be done? 

Here is how I am trying to solve this.

Create a property calle OLDDATE
Create a custom action that has vbscript which runs before the above the
exe's custom action. 
My VBScript custom action looks like this. This is throwing an error. I
tried without set. No luck. Any way of fixing this and any other smart
of doing this ? Thanks in Advance 

CustomAction Id=CalcOldDate Script=vbscript
  SUB CalcMigratorDate()  
   set Session.Property(OLDDATE) = DateAdd(d,-30,DateValue(Now))
  End SUB
  call CalcMigratorDate
/CustomAction

--
This message w/attachments (message) may be privileged, confidential or 
proprietary, and if you are not an intended recipient, please notify the 
sender, do not use or share it and delete it. Unless specifically indicated, 
this message is not an offer to sell or a solicitation of any investment 
products or other financial product or service, an official confirmation of any 
transaction, or an official statement of Merrill Lynch. Subject to applicable 
law, Merrill Lynch may monitor, review and retain e-communications (EC) 
traveling through its networks/systems. The laws of the country of each 
sender/recipient may impact the handling of EC, and EC may be archived, 
supervised and produced in countries other than the country in which you are 
located. This message cannot be guaranteed to be secure or error-free. 
References to Merrill Lynch are references to any company in the Merrill 
Lynch  Co., Inc. group of companies, which are wholly-owned by Bank of America 
Corporation. Secur
 ities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed 
* May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking 
Service or Activity * Are Not Insured by Any Federal Government Agency. 
Attachments that are part of this E-communication may have additional important 
disclosures and disclaimers, which you should read. This message is subject to 
terms available at the following link: 
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you 
consent to the foregoing.
--
 

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

Bob Arnson-6 wrote:

Roy Abou Assaly wrote:
Value=00 01 gives:

error LGHT0204 : ICE70: The value '#x01 02' is an invalid hexadecimal
value
for registry entry regA16537AC885C7B5BB23019846BB931C1.
Value=00;01 gives:
error LGHT0204 :ICE70: The value '#x01;02' is an invalid hexadecimal
value
for registry entry regA16537AC885C7B5BB23019846BB931C1.
Value={01 02}
error LGHT0204 : ICE70: The value '#x{01 02}' is an invalid hexadecimal
value for registry entry regA16537AC885C7B5BB23019846BB931C1.

Hmmm...any other suggestions? If regedit expects a comma, is there some
character replacement for it that WiX would want?

WiX isn't complaining; the ICE validators are. Did you try no delimiters
at all? (RegEdit isn't authoritative.)

--
sig://boB
http://joyofsetup.com/

Suppressing the ICE070 validator gets me past that point. But when I try to
install, I get the following error message:

Could not write value SomeBinaryValue to key \SOFTWARE\Foo\Bar. Verify
that you have sufficient access to that key, or contact your support
personnel.

I obviously have access, so it looks like it doesn't like 00 01 or {00
01} or {01,02} or {01, 02} are working.

--
View this message in context:
http://n2.nabble.com/Writing-a-Value-for-RegistryValue-element-of-Type-Binary-tp2378965p2379918.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

Roy Abou Assaly wrote:

Bob Arnson-6 wrote:

Roy Abou Assaly wrote:
Value=00 01 gives:

Hmmm...any other suggestions? If regedit expects a comma, is there some
character replacement for it that WiX would want?

WiX isn't complaining; the ICE validators are. Did you try no delimiters
at all? (RegEdit isn't authoritative.)

--
sig://boB
http://joyofsetup.com/

Suppressing the ICE070 validator gets me past that point. But when I try
to install, I get the following error message:

Could not write value SomeBinaryValue to key \SOFTWARE\Foo\Bar. Verify
that you have sufficient access to that key, or contact your support
personnel.

I obviously have access, so it looks like it doesn't like 00 01 or {00
01} or {01,02} or {01, 02} are working.

Just to be clear. It is NOT working. Forgot to proofread my post.
--
View this message in context:
http://n2.nabble.com/Writing-a-Value-for-RegistryValue-element-of-Type-Binary-tp2378965p2379981.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Writing a Value for RegistryValue element of Type Binary

Roy Abou Assaly wrote:

Bob Arnson-6 wrote:

Roy Abou Assaly wrote:
Value=00 01 gives:

Hmmm...any other suggestions? If regedit expects a comma, is there
some
character replacement for it that WiX would want?

WiX isn't complaining; the ICE validators are. Did you try no delimiters
at all? (RegEdit isn't authoritative.)

--
sig://boB
http://joyofsetup.com/

Suppressing the ICE070 validator gets me past that point. But when I try
to install, I get the following error message:

Could not write value SomeBinaryValue to key \SOFTWARE\Foo\Bar. Verify
that you have sufficient access to that key, or contact your support
personnel.

I obviously have access, so it looks like it doesn't like 00 01 or {00
01} or {01,02} or {01, 02} are working.

Just to be clear. It is NOT working. Forgot to proofread my post.

SOLUTION: You were right. My brain was stuck. No delimiter is the correct
way. My solution was some like this:

d RegistryValue Type=binary
Name=SomeBinaryValue
Value=0140032001c00010002801400ff010f0001010001020064001400fd0102000101000512001800ff010f00010200052000200214008d010200010100050b001800fd0102000102000520002302010100051200010100051200
KeyPath=yes/

Thanks for the help!

--
View this message in context:
http://n2.nabble.com/Writing-a-Value-for-RegistryValue-element-of-Type-Binary-tp2378965p2380024.html
Sent from the wix-users mailing list archive at Nabble.com.

[WiX-users] How to make the UI Dialog RightToLeft when installing on an machine with Arabic lenguage?

2009-02-24 Thread Tom Tseng

Hi,

I tried by adding RightToLeft=yes to the one of the Dialogs and its Control's 
attribute without any success.  Are there other things I need to do to make it 
happens?

Thanks,
Tom
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using WiX in a Team Build Environment

2009-02-24 Thread Lee Baker

Hi Neil,

Thanks so much for your pointer. That worked a treat, and makes me think I
am a bit of a duffer for not finding it earlier.

Cheers

Lee


*Re: [WiX-users] Using WiX in a Team Build Environment*
From: Neil Sleightholm n...@x2... - 2009-02-24 07:18
  Have you tried using the built in project references:
http://wix.sourceforge.net/manual-wix3/votive_project_references.htm. I
believe they work in a TFS build.

Neil

-Original Message-
From: Lee Baker [mailto:lee.re...@gm...]
Sent: 24 February 2009 05:41
To: wix-us...@li...
Subject: [WiX-users] Using WiX in a Team Build Environment

Hi,
I have been searching for the last few hours and haven't been able to
find
anything describing how to use WiX in a team build environment.

My problem is that the file source location is not available when built
using the tfsbuild server, if I set it using the source in my
environment.
eg. ../proj name/bin/build type/file name.exe

When I set this location I get the error
error LGHT0103: The system cannot find the file '../proj
name/bin/build
type/file name.exe'
for all the files I define this way.

One work around I was considering was building the files to a common
folder
in the root of the solution, however this isn't as neat as using
environment
variables that are set by the build.

I hope I have been clear enough in my description.

Any help is much appreciated.

Thanks

Lee


There's a difference between a philosophy and a bumper sticker.
Charles M. Schulz
There's a difference between a philosophy and a bumper sticker.
   Charles M. Schulz
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Question: How to get the complete value of target dir

2009-02-24 Thread Nan Zang

I am going to write a registry key value which is supposed to be

c:\program files\my product\eventmessages.dll.  My target dir is c:\program 
files\my product.

However, when I use the following statement in the wix:

Registry Id=EventMessageFile
  Name=EventMessageFile
  Action=write
  Type=expandable
  Value=[TargetDir]\EventMessages.dll /

The regkey value is set to be \EventMessages.dll. The value of targetdir is 
omitted.

Is there any way I can retrieve the complete value of targetdir.

Thanks a lot, 

Nan

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Date calculations

2009-02-24 Thread Reddy, Mallikarjun (GWM-CAI)

Thanks John. That helped

-Original Message-
From: John Nannenga [mailto:john.nanne...@microsoft.com] 
Sent: Tuesday, February 24, 2009 2:40 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Date calculations

DateAdd returns a date, Session.Property must take a string, hence the
type mismatch error you were likely receiving.

Try this instead... Use FormatDateTime to convert your date object...

CustomAction Id=CalcOldDate Script=vbscript
  SUB CalcMigratorDate
  Session.Property(OLDDATE) =
FormatDateTime(DateAdd(d,-30,DateValue(Now)))
  End SUB
  call CalcMigratorDate
/CustomAction


Standard disclaimer regarding script CAs goes here, though I didn't
realize WiX made them so darn easy to add/use!/


-Original Message-
From: Reddy, Mallikarjun (GWM-CAI) [mailto:mallikarjun_re...@ml.com] 
Sent: Tuesday, February 24, 2009 12:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Date calculations

Hello, 

In a custom action, I am going to run an exe with args. One of the args
is a date that is 30 days older than today. Could some let me know how
this could be done? 

Here is how I am trying to solve this.

Create a property calle OLDDATE
Create a custom action that has vbscript which runs before the above the
exe's custom action. 
My VBScript custom action looks like this. This is throwing an error. I
tried without set. No luck. Any way of fixing this and any other smart
of doing this ? Thanks in Advance 

CustomAction Id=CalcOldDate Script=vbscript
  SUB CalcMigratorDate()  
   set Session.Property(OLDDATE) = DateAdd(d,-30,DateValue(Now))
  End SUB
  call CalcMigratorDate
/CustomAction


--
This message w/attachments (message) may be privileged, confidential or
proprietary, and if you are not an intended recipient, please notify the
sender, do not use or share it and delete it. Unless specifically
indicated, this message is not an offer to sell or a solicitation of any
investment products or other financial product or service, an official
confirmation of any transaction, or an official statement of Merrill
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and
retain e-communications (EC) traveling through its networks/systems. The
laws of the country of each sender/recipient may impact the handling of
EC, and EC may be archived, supervised and produced in countries other
than the country in which you are located. This message cannot be
guaranteed to be secure or error-free. References to Merrill Lynch are
references to any company in the Merrill Lynch  Co., Inc. group of
companies, which are wholly-owned by Bank of America Corporation. Secur
 ities and Insurance Products: * Are Not FDIC Insured * Are Not Bank
Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a
Condition to Any Banking Service or Activity * Are Not Insured by Any
Federal Government Agency. Attachments that are part of this
E-communication may have additional important disclosures and
disclaimers, which you should read. This message is subject to terms
available at the following link:
http://www.ml.com/e-communications_terms/. By messaging with Merrill
Lynch you consent to the foregoing.

--
 


--
Open Source Business Conference (OSBC), March 24-25, 2009, San
Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the
Enterprise
-Strategies to boost innovation and cut costs with open source
participation
-Receive a $600 discount off the registration fee with the source code:
SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Open Source Business Conference (OSBC), March 24-25, 2009, San
Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the
Enterprise
-Strategies to boost innovation and cut costs with open source
participation
-Receive a $600 discount off the registration fee with the source code:
SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H

Re: [WiX-users] Question: How to get the complete value of target dir

2009-02-24 Thread Wilson, Phil

Spell it properly case-sensitive - TARGETDIR 

Phil Wilson 


-Original Message-
From: Nan Zang [mailto:naz...@exchange.microsoft.com] 
Sent: Tuesday, February 24, 2009 1:30 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question: How to get the complete value of target dir

I am going to write a registry key value which is supposed to be

c:\program files\my product\eventmessages.dll.  My target dir is c:\program 
files\my product.

However, when I use the following statement in the wix:

Registry Id=EventMessageFile
  Name=EventMessageFile
  Action=write
  Type=expandable
  Value=[TargetDir]\EventMessages.dll /

The regkey value is set to be \EventMessages.dll. The value of targetdir is 
omitted.

Is there any way I can retrieve the complete value of targetdir.

Thanks a lot, 

Nan

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Patch uninstall requires the original base MSI and I don't know why

2009-02-24 Thread Tony Juricic

The uninstallable patch is looking for the original MSI that was
extracted from Setup.exe chainer into temporary folder and is since long
gone.

I re-read the docs but I am still clueless as to what caused it. 

 

Naturally, I want to uninstall the patch without requiring the access to
the original RTM MSI.

 

Here is wxs used to create the patch:

 

?xml version=1.0 encoding=windows-1252?

Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;

  

  !-- Path variables --

  ?define APPROOT = C:\wixpatch?

  ?define RTM = $(var.APPROOT)\Build104?

 

  !-- update location(s) need to be updated --

  ?define QFE1 = $(var.APPROOT)\Build111?

 

 

  !-- patch id needs to be updated --

  PatchCreation Id={.}

 AllowMajorVersionMismatches=no

 AllowProductCodeMismatches=no

 CleanWorkingFolder=no 

 WholeFilesOnly=no

 Codepage=1252 

 

  PatchInformation Description=MyPatch

 Keywords=Installer Hotfix Patch

 Comments=MyPatches

 Manufacturer=Me

 Languages=1033

 Compressed=yes

 SummaryCodepage=1252 

 AdminImage=yes/

 

  !-- Build number needs to be updated --

  PatchMetadata Description= Hotfix 111

 DisplayName=My Hotfix 

 TargetProductName=Mine

 ManufacturerName=Me

 MoreInfoURL=http://www.MeMeMe.com;

 Classification=Hotfix 

 AllowRemoval=yes

 OptimizedInstallMode=yes /

 

  Family Name=Patch DiskId=2 MediaSrcProp=PATCH111
SequenceStart=100  

  UpgradeImage  Id=PatchQFE1 SourceFile=$(var.QFE1)\My.msi 

TargetImage Id=PatchRTM Order=1 IgnoreMissingFiles=no
SourceFile=$(var.RTM)\My.msi /

  /UpgradeImage

  /Family 

 

  TargetProductCode Id={} /

 

  PatchProperty Name=PATCH_111 Value=yes /

 

  !-- patch sequence needs to be updated --

 

PatchSequence PatchFamily=MyPatchFamily

 Sequence=1.0.4.0

 Supersede=no /



  /PatchCreation

/Wix

 

 

 

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch uninstall requires the original base MSI and I don't know why

Tony Juricic wrote:
 The uninstallable patch is looking for the original MSI that was
 extracted from Setup.exe chainer into temporary folder and is since long
 gone.

 I re-read the docs but I am still clueless as to what caused it. 
   

You uninstalled a patch: That performs a repair of the unpatched 
product, which usually requires source. Get a verbose log to verify what 
it's looking for.

-- 
sig://boB
http://joyofsetup.com/


--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] How to find for 32 or 64 BIT target machine on fly?

2009-02-24 Thread akash bhatia

Hi,

How can we find for the type of target machine (32 bit or 64 bit)?

Right now am checking for the existence of the folder * [WINDIR]\SysWOW64* ?

Is this the right way to check for type of target machine ?



Thanks,

Akash
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to find for 32 or 64 BIT target machine on fly?

MSI SDK has a list of standard Hardware Properties.  That one is in there.

akash bhatia wrote:
 Hi,

 How can we find for the type of target machine (32 bit or 64 bit)?

 Right now am checking for the existence of the folder * [WINDIR]\SysWOW64* ?

 Is this the right way to check for type of target machine ?



 Thanks,

 Akash
 --
 Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
 -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
 -Strategies to boost innovation and cut costs with open source participation
 -Receive a $600 discount off the registration fee with the source code: SFAD
 http://p.sf.net/sfu/XcvMzF8H
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
   

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] allow user to specify a location

Take a look at how the WIXUI_INSTALLDIR is used in the WiX source code 
for the WixUIExtension.  That should provide a complete (and working!) 
example.

Naga Ram .C wrote:
 I want the installer to allow user to specify a location where it can
 install some set of files. This need not have to be in the same directory
 tree where the application  its dependencies are installed.



 I already using WIXUI_INSTALLDIR property so as to get the installation
 directory to install the exe  its dependencies, like wise I also need to
 get some other location as input from the user to install some set of file
 that need not have to reside under the same root where the application is
 installed.



 Can you pl. suggest?



 Thanks  Regards,

 Nag

 608 448 3116



 --
 Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
 -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
 -Strategies to boost innovation and cut costs with open source participation
 -Receive a $600 discount off the registration fee with the source code: SFAD
 http://p.sf.net/sfu/XcvMzF8H
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
   

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] DTF - install, rollback and uninstall

Good to know I was lying or going senile... or both... yet.  smile/

Neil Sleightholm wrote:
 I have examined the code some more and it follows the model Rob outline and 
 uses component state to determine what to do.

 Neil

 Neil Sleightholm
 X2 Systems Limited
 n...@x2systems.com mailto:n...@x2systems.com


 

 From: Richard [mailto:legal...@xmission.com]
 Sent: Fri 20/02/2009 18:09
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] DTF - install, rollback and uninstall




 In article e66649032ad92b42901bf5835c76a27f9...@harwood.x2systems.com,
 Neil Sleightholm n...@x2systems.com  writes:

   
 I think you missed the point. I can see there are two different entry =
 points, one for install the other for uninstall but what I can't see is =
 the condition that says to run one on install and the other on =
 uninstall. (Using the SQL one was probably a bad example as that has an =
 override condition other don't.)
 

 Yeah, the SQL one might just be a bad example here.  The SQL actions
 are being gated by two different properties: SKIPUNINSTALLSQLDATA and
 SKIPINSTALLSQLDATA.  Although I haven't examined the source to say for
 sure, I'm willing to bet that there are type 51 CAs that set these
 properties appropriately when these actions need to run.  So the do
 this on install, do that on uninstall logic is probably encoded in
 the conditions on the CAs that set the properties SKIPUNINSTALLSQLDATA
 and SKIPINSTALLSQLDATA.
 --
 The Direct3D Graphics Pipeline -- DirectX 9 draft available for download
   http://www.xmission.com/~legalize/book/download/index.html

 Legalize Adulthood! http://blogs.xmission.com/legalize/

 --
 Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
 -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
 -Strategies to boost innovation and cut costs with open source participation
 -Receive a $600 discount off the registration fee with the source code: SFAD
 http://p.sf.net/sfu/XcvMzF8H
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


   

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 what you would prefer.

Robert O'Brien wrote:
 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 having just 
 ExecuteOnInstall=yes in the one and just ExecuteOnUninstall=yes in the 
 other, vs ExecuteOnInstall=yes RollbackOnUninstall=yes in the one and 
 ExecuteOnUninstall=yes RollbackOnInstall=yesin the other.

 So now it seems that if I want to cover RollbackOnUninstall and 
 RollbackOnInstall cases I'll have to add additional duplicate sql:String 
 statements for those cases vs being able to make single statements be dual 
 role statements like we were originally trying to make work.  Is that how 
 things are intended to work or might this be a sql:String statement 
 processing bug?

 -Original Message-
 From: Michael Osmond [mailto:mosm...@baytech.com.au]
 Sent: Wednesday, February 11, 2009 2:29 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: 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 do what I wanted.

 Michael

 -Original Message-
 From: Robert O'Brien [mailto:robert.obr...@microsoft.com]
 Sent: Thursday, 12 February 2009 5:48 AM
 To: 'General discussion for Windows Installer XML toolset.'
 Subject: 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 ( and during component install rollbacks ).


 q1 - is having the sql:String attribute pair ExecuteOnInstall=yes
 RollbackOnUninstall=yes correct to control having the specific setting
 applied during installs and also during component uninstall rollbacks?

 q2 - is having the sql:String attribute pair ExecuteOnUninstall=yes
 RollbackOnInstall=yes correct to control having the specific setting
 applied during uninstalls and also during component install rollbacks?

 From: Robert O'Brien
 Sent: Wednesday, February 11, 2009 11:28 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: 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
 Server=[DATABASESHOST] /

 sql:SqlString Id=CreateLoginNetworkServiceDatabase1
 SqlDb=MasterDatabase SQL=create login [\[]NT AUTHORITY\NETWORK
 SERVICE[\]] from windows ContinueOnError=yes ExecuteOnInstall=yes
 /

 sql:SqlString Id=CreateUserNetworkServiceDatabase1 SqlDb=Database1
 SQL=create user [\[]NT AUTHORITY\NETWORK SERVICE[\]] for login [\[]NT
 AUTHORITY\NETWORK SERVICE[\]] ContinueOnError=yes
 ExecuteOnInstall=yes /

 sql:SqlString Id=AddRoleMembershipNetworkServiceDatabase1
 SqlDb=Database1 SQL=sp_addrolemember 'NSRunService', 'NT
 AUTHORITY\NETWORK SERVICE' ContinueOnError=yes ExecuteOnInstall=yes
 /

 but the following similar sql extensions calls where I have the sql
 login and db user statements making use of a public property value + the
 statements configured to also execute on uninstall rollback, do not
 work?

 Property Id=DATABASESHOSTNAME Value=localhost

 Property Id=DATABASESLOGINLOCALACCOUNT Value=NT AUTHORITY\NETWORK
 SERVICE /

 sql:SqlDatabase Id=Master Database=master
 Server=[DATABASESHOSTNAME] /

 sql:SqlDatabase Id=Database1 Database=MyDeliverableDatabase
 Server=[DATABASESHOSTNAME] /

 sql:SqlString Id=Database1CreateLoginLocalAccount SqlDb=Master
 Sequence=1 SQL=exec('create login
 [\[][DATABASESLOGINLOCALACCOUNT][\]] from windows')
 ExecuteOnInstall=yes RollbackOnUninstall=yes ContinueOnError=yes
 /

 sql:SqlString Id=Database1CreateUserLocalAccount SqlDb=Database1
 Sequence=2 SQL=exec('create user

Re: [WiX-users] Non-adminstrator installation