Re: [WiX-users] Install SQL SERVER 2008 R2 Express

2013-04-18 Thread Neil Sleightholm
You would be better off using burn to do the install of SQL and then launch your MSI (if you search for "wix burn sql express" you should find a few examples). Neil -Original Message- From: Ravishankar [mailto:ravishankar.krishnasw...@idsnext.com] Sent: 19 April 2013 06:10 To: r...@rob

[WiX-users] Install SQL SERVER 2008 R2 Express

2013-04-18 Thread Ravishankar
Hi Rob, need your expertise :-) My installer does a pre-check for SQL SERVER 2008 installation If SQL Server not found i need to invoke a *.bat file which has the silent unattended installation SQL Server 2008 R2 Express which i have prepared Please help me when and how i

Re: [WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

2013-04-18 Thread uni
于 18/04/2013 21:42, Rob Mensching 写道: > People guessing the SQL influence are correct. Back in 1995, SQL was a big > thing and transacted install was the big new idea (a very good idea, IMHO) > so there was a theory that you should make the MSI a SQL database because > you're doing transaction stuf

Re: [WiX-users] Wix ExePackage can't activate log using Burn

2013-04-18 Thread Marco Tognacci
Do you have any example about enabling logging of ExePackage in Burn chain?I have tried to use LogPathVariable="MyExe.log" but the log doesn't work. > From: mark...@live.it > To: wix-users@lists.sourceforge.net > Date: Wed, 17 Apr 2013 20:57:07 +0200 > Subject: [WiX-users] Wix ExePackage can't a

Re: [WiX-users] PayloadGroupRef as child of Bundle (WiX 3.6)

2013-04-18 Thread tom
add PackageGroupRef inside the chain -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PayloadGroupRef-as-child-of-Bundle-WiX-3-6-tp7585152p7585281.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

2013-04-18 Thread Rob Mensching
People guessing the SQL influence are correct. Back in 1995, SQL was a big thing and transacted install was the big new idea (a very good idea, IMHO) so there was a theory that you should make the MSI a SQL database because you're doing transaction stuff. IMHO, that didn't work out nearly as well a

Re: [WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

2013-04-18 Thread Pally Sandher
Probably a combination of the 2. MSI's are basically databases so I wouldn't be surprised if SQL influenced some parts of Windows Installer design back in the day. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simu

Re: [WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

2013-04-18 Thread John Ludlow
<> is also the syntax in Visual Basic, and VB / VBA has always had strong ties to Office, which is where MSI originated from IIRC. On 18 April 2013 13:35, Hans ter Horst wrote: > Thanks, I think I have it working! > > > > On Thu, Apr 18, 2013 at 2:13 PM, Alain Forget wrote: > > > <> is the MyS

Re: [WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

2013-04-18 Thread Hans ter Horst
Thanks, I think I have it working! On Thu, Apr 18, 2013 at 2:13 PM, Alain Forget wrote: > <> is the MySQL (and SQL in general?) "not equal to", so maybe that's > where it came from? > > -Original Message- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: April 18, 2013 06:

Re: [WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

2013-04-18 Thread Alain Forget
<> is the MySQL (and SQL in general?) "not equal to", so maybe that's where it came from? -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: April 18, 2013 06:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Why in Preproces

Re: [WiX-users] Tutorial about handling upgrades in Wix 3.7

2013-04-18 Thread Alain Forget
+1 for MajorUpgrade -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: April 18, 2013 06:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Tutorial about handling upgrades in Wix 3.7 BTW this is covered in the WiX manual unde

Re: [WiX-users] Registering files

2013-04-18 Thread Pally Sandher
The proper approach would be to not use regsvr32 to register DLL's & OCXs & author the registration info yourself. If you want to make this a lot simpler, use heat.exe to generate the Class, TypeLib & Interface elements for you instead of having reams of RegistryValues -> http://wix.sourceforge.

Re: [WiX-users] Tutorial about handling upgrades in Wix 3.7

2013-04-18 Thread Pally Sandher
BTW this is covered in the WiX manual under the how to's -> http://wix.sourceforge.net/manual-wix3/major_upgrade.htm Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environm

Re: [WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

2013-04-18 Thread Pally Sandher
Because the WiX team wrote the WiX pre-processor syntax & kept it to regularly accepted coding standards (hence != for 'not equal to' as per every other modern programming language) while the Conditional Statement syntax was written by the Windows Installer team back in the mists of time? Palbi