Re: [WiX-users] Combining installations

2007-07-25 Thread Jeroen Davelaar
Thanks Richard for your quick anwser. I will try to build a bootstrapper
for the installation. 

 

One thing I actually also tried was to open the second msi file with
Orca and save it as a merge module. I wanted to try it. It only fails at
the point where light tries to extract the cabinet form the msi. This is
not possible because it has a separate cab file. I'm guessing that even
if that would work there is no chance of getting it to work in this way.


 

Regards

Jeroen Davelaar

 



Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens
[EMAIL PROTECTED]
Verzonden: dinsdag 24 juli 2007 14:21
Aan: Jeroen Davelaar; wix-users@lists.sourceforge.net
Onderwerp: Re: [WiX-users] Combining installations

 

Jeroen,

 

A bootstrapper (also known in some places as a chainer) is the option to
use.

 

Microsoft Installer does not support two simultaneous installations.
(There was a custom action intended to support nested installations, but
it was deprecated long ago. Based on comments from others, I understand
this to have been because it really didn't work properly and the
problems of allowing true nested installations were greater than the
benefit from having that option available.)

 

WiX 3 has (I believe) a partial implementation of a bootstrapper. Other
options include dotNetInstaller
(http://www.codeproject.com/install/dotNetInstaller.asp) NSIS
(http://nsis.sourceforge.net http://nsis.sourceforge.net/ ) and Inno
setup (http://www.jrsoftware.org/isinfo.php). (The last two choices are
actually full installation toolkits, but since they are not MSI based
you can't use them to build the complete setup if you want to meet
Microsoft logo requirements and/or appropriately support customers with
license management tools like Microsoft's Systems Management Server
[SMS].)

 

Regards,

Richard

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeroen
Davelaar
Sent: Tuesday, July 24, 2007 4:40 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Combining installations

 

I'm looking for a good way to include/embed/combine 2 installations. I
have an installation that depends on the product of a different vendor.
The second installation is only available as an MSI package. My wish is
to fully combine the installations, so the users can also pick the
components in the second package from my installation. Is this possible?
What are the alternatives; bootstrapper or a customaction that installs
the second package? 

 

I'm just a beginner in WiX so I would also like to know the pro's and
con's of the solutions. I hope this question hasn't been asked before
but the search server seems to be down so i'm not able to search the
mailinglists.

 

Thanks
Jeroen Davelaar




* C O N F I D E N T I A L I T Y N O T I C E *
---
The content of this e-mail is intended solely for the use of the
individual or entity to whom it is addressed. If you have received this
communication in error, be aware that forwarding it, copying it, or in
any way disclosing its content to any other person, is strictly
prohibited. Quixote Traffic Corporation is neither liable for the
contents, nor for the proper, complete and timely transmission of (the
information contained in) this communication. If you have received this
communication in error, please notify the author by replying to this
e-mail immediately and delete the material from any computer.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] How to change TARGETDIR to e drive

2007-07-25 Thread Ravit Shapira
 Hi,

I'm trying to change TARGETDIR to e drive.  I tried to do the following but it 
installs under c drive.

CustomAction Id=AssignEDir2INSTALLDIR Directory=TARGETDIR Value=E:\ 
Execute=firstSequence /
InstallExecuteSequence
  Custom Action=AssignEDir2INSTALLDIR 
After=CostFinalizeTARGETDIR=E:\/Custom
/InstallExecuteSequence

I ran the installation using msiexec and created a log file. I looked for the 
action: AssignEDir2INSTALLDIR and it says that it is skipped due to false 
condition.


 1.  Do you have an explanation why the condition is false? I do have e drive 
in the computer that I use.
 2.  How can I fix this problem? All I need is to change the default value of 
TARGETDIR from c:\ to e:\


Thank you in advance,
Ravit


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to change TARGETDIR to e drive

2007-07-25 Thread Ravit Shapira
 Hi,

I want to add to my previous email that if I run the installation using:  
msiexec /i MySetup.msi TARGETDIR=e:\ it does installs what I need under e 
drive.
However, my goal is to run the setup without passing any parameters - simply to 
double click on the msi file.

Thanks,
Ravit

From: Ravit Shapira
Sent: Tuesday, July 24, 2007 11:38 PM
To: 'wix-users@lists.sourceforge.net'
Subject: How to change TARGETDIR to e drive

 Hi,

I'm trying to change TARGETDIR to e drive.  I tried to do the following but it 
installs under c drive.

CustomAction Id=AssignEDir2INSTALLDIR Directory=TARGETDIR Value=E:\ 
Execute=firstSequence /
InstallExecuteSequence
  Custom Action=AssignEDir2INSTALLDIR 
After=CostFinalizeTARGETDIR=E:\/Custom
/InstallExecuteSequence

I ran the installation using msiexec and created a log file. I looked for the 
action: AssignEDir2INSTALLDIR and it says that it is skipped due to false 
condition.


 1.  Do you have an explanation why the condition is false? I do have e drive 
in the computer that I use.
 2.  How can I fix this problem? All I need is to change the default value of 
TARGETDIR from c:\ to e:\


Thank you in advance,
Ravit


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to change TARGETDIR to e drive

2007-07-25 Thread Mailinglist
Hi,

you want to launch the custom action, that assigns E:\ to TARGETDIR only if 
TARGETDIR has the value E:\. Your Condition is wrong.

In our setup we use a Property that determines if drive e is present and if so, 
sets the default install path to e, maybe this is something for you either.

Property Id='NEWINSTALLDIR' Value='C:\'
  DirectorySearch Id='MSEwsDefaultInstallRoot_Search' Path='E:\' 
Depth='1'/
/Property

CustomAction Id=DirectorySet Property=TARGETDIR Value=[NEWINSTALLDIR]\ /

InstallExecuteSequence
Custom Action='DirectorySet' Before='LaunchConditions'NOT TARGETDIR/Custom
/InstallExecuteSequence

Oliver.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ravit Shapira
Sent: Mittwoch, 25. Juli 2007 08:46
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to change TARGETDIR to e drive

 Hi,

I want to add to my previous email that if I run the installation using:  
msiexec /i MySetup.msi TARGETDIR=e:\ it does installs what I need under e 
drive.
However, my goal is to run the setup without passing any parameters - simply to 
double click on the msi file.

Thanks,
Ravit

From: Ravit Shapira
Sent: Tuesday, July 24, 2007 11:38 PM
To: 'wix-users@lists.sourceforge.net'
Subject: How to change TARGETDIR to e drive

 Hi,

I'm trying to change TARGETDIR to e drive.  I tried to do the following but it 
installs under c drive.

CustomAction Id=AssignEDir2INSTALLDIR Directory=TARGETDIR Value=E:\ 
Execute=firstSequence /
InstallExecuteSequence
  Custom Action=AssignEDir2INSTALLDIR 
After=CostFinalizeTARGETDIR=E:\/Custom
/InstallExecuteSequence

I ran the installation using msiexec and created a log file. I looked for the 
action: AssignEDir2INSTALLDIR and it says that it is skipped due to false 
condition.


 1.  Do you have an explanation why the condition is false? I do have e drive 
in the computer that I use.
 2.  How can I fix this problem? All I need is to change the default value of 
TARGETDIR from c:\ to e:\


Thank you in advance,
Ravit


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] customactions and installsequence

2007-07-25 Thread Frédéric Viollet

Ok. Thanks.
I scheduled the action as deferred after InstallFiles (I needed the 
custom action to be triggered after file installation and before service 
start). I works fine.

Thanks again for your help.

Fred

Mike Dimmick a écrit :

Sorry, either mark as deferred and schedule between InstallInitialize and
InstallFinalize, or mark as immediate and schedule after InstallFinalize. If
you try to schedule a deferred action after InstallFinalize I believe you'll
get a runtime error.

If you use an immediate action after InstallFinalize your action cannot
cause the install to roll back (because the transaction has already been
committed).

  


begin:vcard
fn;quoted-printable:Fr=C3=A9d=C3=A9ric Viollet
n;quoted-printable:Viollet;Fr=C3=A9d=C3=A9ric
org:Bull, Architect of an Open World (TM);Evidian S.A.
adr;quoted-printable:;;Rue Jean Jaur=C3=A8s;Les Clayes Sous Bois;;78340;France
email;internet:[EMAIL PROTECTED]
title:Software Engineer
tel;work:01 30 80 77 34
url:http://www.evidian.com - http://www.bull.com
version:2.1
end:vcard

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] custom dialog set build with nant error

2007-07-25 Thread bryan rasmussen
but not in the binaries? Should I need it if I am running the
binaries? Well I guess I'll get the source anyway and see how it
works.

Cheers,
Bryan Rasmussen

On 7/25/07, Bob Arnson [EMAIL PROTECTED] wrote:
 bryan rasmussen wrote:
  nant gives the following error: Build File c:\tools\wix.include does not 
  exist.
 
  I suppose in reference to this include.
include buildfile=..\..\..\..\wix.include
  unless=${property::exists('wix.properties.defined')} /
 
  so, two questions where are the includes in the example? and how do I
 

 wix.include is in the root of the WiX source.

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




-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Emilien Bertin
Thanks for the confirmation Bob.
So I have to drop this msi in msi solution because I want to deliver a 
msi, not an external .exe

Do you have an other idea ? At least I would like the big part to be an 
msi, and the small one could be a zip or something.



Bob Arnson a écrit :
 Emilien Bertin wrote:
 So I want the big msi to install the 2 msi. I employ the CustomAction 
 type 50 (with [SystemFolder]msiexec and /quiet /i 
 path_to_small_msi ). But it seems impossible to install two msi in 
 the same time. 
 
 That's correct. You need to use an external .exe bootstrapper.
 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Bernd
thats not correct!

you dont need the external exe.

with custom action type 7/23/39 you can nest a msi.

http://support.microsoft.com/default.aspx/kb/306439



Emilien Bertin wrote:
 Thanks for the confirmation Bob.
 So I have to drop this msi in msi solution because I want to deliver a 
 msi, not an external .exe

 Do you have an other idea ? At least I would like the big part to be an 
 msi, and the small one could be a zip or something.



 Bob Arnson a écrit :
   
 Emilien Bertin wrote:
 
 So I want the big msi to install the 2 msi. I employ the CustomAction 
 type 50 (with [SystemFolder]msiexec and /quiet /i 
 path_to_small_msi ). But it seems impossible to install two msi in 
 the same time. 
   
 That's correct. You need to use an external .exe bootstrapper.
 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] How to change TARGETDIR to e drive

2007-07-25 Thread Friedrich Brunzema
Ravit,

looks like you have a condition on your custom action;  I think that 
Custom Action=AssignEDir2INSTALLDIR 
After=CostFinalizeTARGETDIR=E:\/Custom
means do the custom action only if TARGETDIR=E:\.  Try changing this the 
TARGETDIR=E:\ condition to 1, meaning it will always be executed.

Friedrich


 Hi,

I'm trying to change TARGETDIR to e drive.  I tried to do the following but it 
installs under c drive.

CustomAction Id=AssignEDir2INSTALLDIR Directory=TARGETDIR Value=E:\ 
Execute=firstSequence /
InstallExecuteSequence
  Custom Action=AssignEDir2INSTALLDIR 
After=CostFinalizeTARGETDIR=E:\/Custom
/InstallExecuteSequence









  Get news delivered with the All new Yahoo! Mail.  Enjoy RSS feeds right 
on your Mail page. Start today at http://mrd.mail.yahoo.com/try_beta?.intl=ca-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Unknown preprocessor statements

2007-07-25 Thread John Hall
Should the WiX preprocessor give an error if there is a statement that
it does not recognise?
 
I just spent some time tracking down a problem, which eventually came
down to me using ?elsif ? rather than ?elseif ?. An error message
saying ?elsif was not recognised would have been useful.
 
Regards,
John
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Set property from registry search

2007-07-25 Thread Benas

I have tried to search registry using this:
Property Id=MYAPPPATH2RegistrySearch Id='SearchRegistry' Type='raw'
Root='HKLM' Key='Software\a\b' Name='PathName' //Property

And then tried to build to installers one with:
Condition Message='Error''MYAPPPATH2/Condition
And another with:
Condition Message='Error''NOT MYAPPPATH2/Condition

In both cases Error message box came up. How can it be?

in both cases i was using:
   InstallExecuteSequence
 LaunchConditions After='AppSearch' /
 RemoveExistingProducts After='InstallFinalize' /
   /InstallExecuteSequence




I want to install my program to directory set in registry value but can't
find any working example.
If i set my property like
Property Id=MYAPPPATH2d:\a\/Property
Then everything works.

But then i use registry search - it doesn't.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Jeroen Davelaar
How is it possible to nest a msi file with Orca while it is nog possible to do 
the same thing with WiX? 

Regards,
Jeroen Davelaar 


-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Bernd
Verzonden: woensdag 25 juli 2007 13:47
Aan: Emilien Bertin; WiX-users@lists.sourceforge.net
Onderwerp: Re: [WiX-users] Msi inside msi ?

thats not correct!

you dont need the external exe.

with custom action type 7/23/39 you can nest a msi.

http://support.microsoft.com/default.aspx/kb/306439



Emilien Bertin wrote:
 Thanks for the confirmation Bob.
 So I have to drop this msi in msi solution because I want to deliver a 
 msi, not an external .exe

 Do you have an other idea ? At least I would like the big part to be an 
 msi, and the small one could be a zip or something.



 Bob Arnson a écrit :
   
 Emilien Bertin wrote:
 
 So I want the big msi to install the 2 msi. I employ the CustomAction 
 type 50 (with [SystemFolder]msiexec and /quiet /i 
 path_to_small_msi ). But it seems impossible to install two msi in 
 the same time. 
   
 That's correct. You need to use an external .exe bootstrapper.
 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] WIX SqlScript tag

2007-07-25 Thread Arnold Layne

Hi all,

How do I pass paramteres to my sql script? I would like to do something
similar to what is done by sqlcmd:
SQLCMD MyScript.sql -v Param1=Value1 -v Param2=Value2 ...

Can I do it in WIX ver 2 with the SqlScript tag?

Thanks
-al
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] How to declare optional - but exclusive - components?

2007-07-25 Thread Crusty Applesniffer
Hello,
I'm using Wix3.0 and I wonder if there is a way to declare two 
components that can not be installed for the same feature.
I mean how can I have:
(x) Feature 1
(x) Component A
(  ) Component B

that automatically changes to :
(x) Feature 1
(  ) Component A
(x) Component B

when the user selects component B (and vice-versa)

Thank you

Crusty Applesniffer



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Richard.Foster
Bernd,

While it is not documented in the article you reference (but probably should 
be) custom action types 7, 23 and 39 are deprecated.

For more details, see the various blog entries by the windows installer team - 
especially 
http://blogs.msdn.com/windows_installer_team/archive/2006/11/06/q-a-from-latest-windows-installer-webcast-available.aspx
 where they state Nested installs are still supported in [Windows Installer] 
4.0. Concurrent Installations, also called Nested Installations, is a 
deprecated feature of the Windows Installer. Applications installed with 
concurrent installations can eventually fail because they are difficult for 
customers to service correctly. Do not use concurrent installations to install 
products that are intended to be released to the public.

Regards,
Richard

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernd
Sent: Wednesday, July 25, 2007 7:47 AM
To: Emilien Bertin; WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Msi inside msi ?

thats not correct!

you dont need the external exe.

with custom action type 7/23/39 you can nest a msi.

http://support.microsoft.com/default.aspx/kb/306439



Emilien Bertin wrote:
 Thanks for the confirmation Bob.
 So I have to drop this msi in msi solution because I want to deliver a 
 msi, not an external .exe

 Do you have an other idea ? At least I would like the big part to be an 
 msi, and the small one could be a zip or something.



 Bob Arnson a écrit :
   
 Emilien Bertin wrote:
 
 So I want the big msi to install the 2 msi. I employ the CustomAction 
 type 50 (with [SystemFolder]msiexec and /quiet /i 
 path_to_small_msi ). But it seems impossible to install two msi in 
 the same time. 
   
 That's correct. You need to use an external .exe bootstrapper.
 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



* C O N F I D E N T I A L I T Y N O T I C E *
---
The content of this e-mail is intended solely for the use of the individual or 
entity to whom it is addressed. If you have received this communication in 
error, be aware that forwarding it, copying it, or in any way disclosing its 
content to any other person, is strictly prohibited. Quixote Traffic 
Corporation is neither liable for the contents, nor for the proper, complete 
and timely transmission of (the information contained in) this communication. 
If you have received this communication in error, please notify the author by 
replying to this e-mail immediately and delete the material from any computer.



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Uninstalling IIS VDirs from deleted website...

2007-07-25 Thread david adams
I could be wrong, but I believe that if the website / vdir is recreated in 
IIS, you could run the uninstall.


David Adams
MSN MessengerID: [EMAIL PROTECTED]






Anyone have suggestions on how to handle the situation where setup fails on 
uninstall because the website associated with a virtual directory no longer 
exists?  It is possible for users to re-create the website in IIS manager 
and then run uninstall, but it seems it would be better to simply ignore 
that the virtual directory/web site is missing and continue on with setup 
(same as would happen if an installed file was missing during uninstall).

Anyone have ideas about the best way to resolve this issue?

Thanks,
Micah



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/


___
WiX-users mailing list

https://lists.sourceforge.net/lists/listinfo/wix-users

_
http://imagine-windowslive.com/hotmail/?locale=en-usocid=TXT_TAGHM_migration_HM_mini_pcmag_0507


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] custom dialog set build with nant error

2007-07-25 Thread Bob Arnson
bryan rasmussen wrote:
 but not in the binaries? Should I need it if I am running the
 binaries? 

If you want to build something from the WiX source, yes. WiX v3 improved 
how custom objects and libraries can reuse existing ones.

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



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Bob Arnson
Emilien Bertin wrote:
 Do you have an other idea ? At least I would like the big part to be an 
 msi, and the small one could be a zip or something.
   

I'm not sure I understand the scope of the problem. WiX works just like 
every other compiler/linker in that it's scriptable so rebuilding an MSI 
to include new files is easily automatable. What do you gain by trying 
to separate?

That's a long way of saying I don't know of a better solution if you 
want to ship just one MSI.

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



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to declare optional - but exclusive - components?

2007-07-25 Thread Bob Arnson
Crusty Applesniffer wrote:
 I'm using Wix3.0 and I wonder if there is a way to declare two 
 components that can not be installed for the same feature.
 I mean how can I have:
 (x) Feature 1
 (x) Component A
 (  ) Component B

 that automatically changes to :
 (x) Feature 1
 (  ) Component A
 (x) Component B

 when the user selects component B (and vice-versa)
   

It's not clear what you're looking for. Users don't select components -- 
the setup developer specifies which components belong to which features. 
Do you want a UI control?

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



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Unknown preprocessor statements

2007-07-25 Thread Bob Arnson

John Hall wrote:
Should the WiX preprocessor give an error if there is a statement that 
it does not recognise?
 
I just spent some time tracking down a problem, which eventually came 
down to me using ?elsif ? rather than ?elseif ?. An error message 
saying ?elsif was not recognised would have been useful.


I would have assumed so but there's a comment in the current 
preprocessor code that says:


default:
   // unknown processing instructions are currently ignored
   break;

Seems ugly to me and by currently, I'd say it's open to a 
nicely-worded feature request.g I assume it's there for extensibility 
but extensibility was added via preprocessor extension which requires a 
prefix...


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

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Bob Arnson
Jeroen Davelaar wrote:
 How is it possible to nest a msi file with Orca while it is nog possible to 
 do the same thing with WiX? 
   

WiX deprecated the functionality when the MSI team deprecated it.

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


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] How to declare optional - but exclusive - components?

2007-07-25 Thread Crusty Applesniffer
Sorry,


Feature Id=Complete Title=Complete Display=expand Level=1 
ConfigurableDirectory=INSTALLLOCATION
  Feature Id=MainConsoleProgramCompleteFeat Title=Main Console 
Level=1
ComponentRef Id=MainConsole /
  /Feature
  Feature Id=KernelCompleteFeat Title=Service Level=1
ComponentRef Id=KernelComponent /
  /Feature
  Feature Id=Alternate1SvcCompleteFeat Title=Service N°1 Level=1
ComponentRef Id=Svc1Component /
ComponentRef Id=Svc1Interface/
  /Feature
  Feature Id=Alternate2SvcCompleteFeat Title=Service N°2 Level=1
ComponentRef Id=Svc2Component /
ComponentRef Id=Svc2Interface/
  /Feature
/Feature


If user selects Service N°2 during installation, Service N°1 feature 
will be unselected.
If user selects Service N°1 during installation, Service N°2 feature 
goes back to unselected

(I hope it is clearer, sorry)

Bob Arnson wrote:
 Crusty Applesniffer wrote:
   
 I'm using Wix3.0 and I wonder if there is a way to declare two 
 components that can not be installed for the same feature.
 I mean how can I have:
 (x) Feature 1
 (x) Component A
 (  ) Component B

 that automatically changes to :
 (x) Feature 1
 (  ) Component A
 (x) Component B

 when the user selects component B (and vice-versa)
   
 

 It's not clear what you're looking for. Users don't select components -- 
 the setup developer specifies which components belong to which features. 
 Do you want a UI control?

   



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] beginning with Wix - which version?

2007-07-25 Thread Alan Sinclair




If I'm moving to WiX, which version should I use. How far off is stable
v3 likely to be?

A colleague said "I would wait
for a stable 3.0 before considering switching. Its vastly
improved over version 2, and is not backwards
compatible."

Thanks




-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WIX SqlScript tag

2007-07-25 Thread Dana Gutride

We do this using public properties and the SqlString element instead.  You
end up embedding the actual sql directly in the MSI, but you can reference
the properties directly.  An example follows:

SqlString Sequence=3 Id=AddRoles SQL=Use [DBNAME]
 exec sp_addrolemember N'db_owner', N'UserName'
   ExecuteOnInstall=yes ExecuteOnUninstall=no SqlDb=SqlDB/

Dana

On 7/25/07, Arnold Layne [EMAIL PROTECTED] wrote:


Hi all,

How do I pass paramteres to my sql script? I would like to do something
similar to what is done by sqlcmd:
SQLCMD MyScript.sql -v Param1=Value1 -v Param2=Value2 ...

Can I do it in WIX ver 2 with the SqlScript tag?

Thanks
-al

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Sample for preventing the installer from continuing when a particular process/application is running?

2007-07-25 Thread Lawrence Hodson
Hello

 

I'm using WiX v3 for an Outlook 2007 addin, but I've got to a point
where I'm completely stuck.

 

My installer works ok, but I now need to ensure our it doesn't proceed
while Office 2007 apps (particularly Outlook.exe) are running.  I'm yet
to find a complete explanation or example of how to actually do this. So
far I've gleemed that I'd need a CustomAction do do this.  I have also
seen suggestions that the CustomAction could populate the FilesInUse
dialog somehow.

 

I also hear that CustomActions must be done in C++.  As a .NET developer
this is a bit of a problem.  

 

Can anyone please point me in the right direction  show me the C++
source code to do what I need?

 

 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Unicode and troubles

2007-07-25 Thread Magus

Is there any way to convert Unicode to said code page via code? I am lucky
enough to be using an external UI.  There is only 1 dialog (Disk Cost) that
is displays internally.  Is there a way to get the information that a Disk
Cost dialog would display from the MSI?

Bob Arnson-6 wrote:
 
 Magus wrote:
 I just reciently found out that it might not be possible to use Unicode
 and I
 would need to use code pages :( .  I've been working with this about a
 year
 now.  I really don't understand the whole code page thing and all the
 strings I need are using Unicode.  I really have no idea what I am doing
 or
 how to make something that works with this thing.
   
 
 MSI databases don't support Unicode. See 
 http://blogs.msdn.com/robmen/archive/2004/11/22/268343.aspx and 
 http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/localizing_a_windows_installer_package.asp
  
 for some details about localization.
 
 -- 
 sig://boB
 http://joyofsetup.com/
 
 
 
 -
 This SF.net email is sponsored by: Splunk Inc.
 Still grepping through log files to find problems?  Stop.
 Now Search log events and configuration files using AJAX and a browser.
 Download your FREE copy of Splunk now   http://get.splunk.com/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

-- 
View this message in context: 
http://www.nabble.com/Unicode-and-troubles-tf4132589.html#a11800186
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] subscribe

2007-07-25 Thread Don Tasanasanta (Volt)

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] How to automated uninstall?

2007-07-25 Thread LEMIRE, JOHN
I'm wondering if anyone's run into this before and has a best practice
solution.
 
The scenario is an automated deployment environment that attempts to run
a scheduled upgrade of minor revisions of a product.
Therefore the numbers of the currently installed and to be installed
versions only differ in the revision position.
The major/minor/build positions are identical. This leads msi to not
perform the install as it only looks as far as build to determine
difference.
 
The first reaction to get around this is to try uninstall/reinstall
instead of upgrade, however uninstall seems to require either the
original msi file (no longer present) or the ProductCode.
 
Being a good wix citizen I have set my Product Id=* .../ which means
new ProductCode for every build and makes it hard to script uninstall by
ProductCode.
Is there a way to achieve the unistall that I'm overlooking? Getting the
build portion of the version number changed is beyond my control and
even new minor revisions do need to be deployed for testing.
 
thanks
-john
 
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] WindowsVolume Directory

2007-07-25 Thread Quattro IV

Hello, can anyone point me to a way to get a shortcut installed under the
windows volume folder without getting the following warning?

Here is my directory structure:


Directory Id=WINDOWSVOLUME

Directory Id=ISConfig Name=ISconfig 

Directory Id=AppToolBarDir Name=Applications/

/Directory

/Directory



Here is the warning (note it still compiles and creates my shortcut in the
appropriate place):

Warning 1 ICE46: Property 'WINDOWSVOLUME' referenced in column
'Directory'.'Directory' of row 'WINDOWSVOLUME' differs from a defined
property by case
only. 
C:\RWFSystem\DNA.RadWorkflow\DNA.RadWorkflow.TabletWorklist\Application.TabletWorklist\Installer\TabletWorklist.wxs
10 1 TabletWorklist


Thanks
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Mike Dimmick
WiX was designed to support very large installer projects, with a design
goal of distributed setup authoring. To support this idea, WiX supports
Fragments.

A Fragment is just a section of setup authoring. Loosely, candle compiles
source files containing one or more Fragments into .wixobj files, and light
links one or more .wixobj files into a final installer/merge module/patch.

One, and only one, of the sections of an installation must be a Product,
PatchCreation, or Module.

candle and light are very much modelled after a C/C++ Compiler and Linker
respectively. It took me a while to work out that the first letter of each
tool's name indicates its purpose (Candle = compiler, Light = linker, Lit =
library tool, Dark = decompiler, Heat = 'harvester', Pyro = patch builder,
Torch = transform creation). You can keep .wixobj files between sessions if
the corresponding source file hasn't changed, which may reduce build time
(although most of the cost is in binding and validating the MSI rather than
processing the source files).

A traditional C compiler would only operate on a single source file per run,
but like Microsoft's cl.exe, candle accepts multiple source files on the
same command line.

You should probably consider defining one Fragment per logical component
(not necessarily Component) of your product. Just like C# and C++ classes,
you can have more than one Fragment per source file, but it may be more
understandable if you stick to one Fragment per source file. Splitting your
installation into more source files reduces the chance of checkout/merge
collisions with multiple developers.

In general, Fragments are much nicer to work with than merge modules.

-- 
Mike Dimmick

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Collins, James
Sent: 25 July 2007 19:35
To: Bob Arnson; Jeroen Davelaar
Cc: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Msi inside msi ?

Hey Jeroen,

I'm also not sure what your trying to achieve however for me I
have very large installers including well over 16k files. For me I need
to split that up to reduce build time as well as keeping things modular.
The way I do that is with Merge Modules (MSM) which is basically an
installer inside an installer.

Jimbo

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, July 25, 2007 8:27 AM
To: Jeroen Davelaar
Cc: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Msi inside msi ?

Jeroen Davelaar wrote:
 How is it possible to nest a msi file with Orca while it is nog
possible to do the same thing with WiX? 
   

WiX deprecated the functionality when the MSI team deprecated it.

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



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] ProjectAggregator2-3.0.2925.msi fails to install with odd network error

2007-07-25 Thread Scott Palmer

I downloaded the latest 3.0 release and when I attempt to install the
project aggregator MSI windows gives me an error message  A network error
occurred while attempting to read from the file C:\ProjectAggregator2.msi

(resending, since list acknowledged receipt but failed to follow through
with delivery)

There are a couple odd things about this.  For one, access to my local C
drive doesn't require any access to the network.  Secondly, the file name
of the msi is C:\ProjectAggregator2- 3.0.2925.msi not the
C:\ProjectAggregator2.msi that is shown in the error message.

It doesn't matter what folder I put the MSI in before I launch it.. the
error message adapts to the folder name, but still has the wrong file name.

So I renamed the file so that it matched the error message and it worked!
Still... that's just plain weird and I don't want it to happen with my own
MSI installers.

(I did have the previous 3.0 release 3.0.2420.0 installed already)

What's going on?


Scott
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Collins, James
Hey Jeroen,

I'm also not sure what your trying to achieve however for me I
have very large installers including well over 16k files. For me I need
to split that up to reduce build time as well as keeping things modular.
The way I do that is with Merge Modules (MSM) which is basically an
installer inside an installer.

Jimbo

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, July 25, 2007 8:27 AM
To: Jeroen Davelaar
Cc: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Msi inside msi ?

Jeroen Davelaar wrote:
 How is it possible to nest a msi file with Orca while it is nog
possible to do the same thing with WiX? 
   

WiX deprecated the functionality when the MSI team deprecated it.

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



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Msi inside msi ?

2007-07-25 Thread Collins, James
Thanks mike,

Yes I would agree fragments offer much more and I will keep that
in mind moving forward. For me however I need a migration path from Wise
to WIX and that's going to be merge modules for now. Once I have
convinced my team WIX is the way to go (and believe me I'm trying very
hard), and we are fully WIX then this approach makes much more sense. 

WIX by stealth! :)

Jimbo 

-Original Message-
From: Mike Dimmick [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 25, 2007 12:02 PM
To: Collins, James; 'Bob Arnson'; 'Jeroen Davelaar'
Cc: WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] Msi inside msi ?

WiX was designed to support very large installer projects, with a design
goal of distributed setup authoring. To support this idea, WiX supports
Fragments.

A Fragment is just a section of setup authoring. Loosely, candle
compiles
source files containing one or more Fragments into .wixobj files, and
light
links one or more .wixobj files into a final installer/merge
module/patch.

One, and only one, of the sections of an installation must be a Product,
PatchCreation, or Module.

candle and light are very much modelled after a C/C++ Compiler and
Linker
respectively. It took me a while to work out that the first letter of
each
tool's name indicates its purpose (Candle = compiler, Light = linker,
Lit =
library tool, Dark = decompiler, Heat = 'harvester', Pyro = patch
builder,
Torch = transform creation). You can keep .wixobj files between sessions
if
the corresponding source file hasn't changed, which may reduce build
time
(although most of the cost is in binding and validating the MSI rather
than
processing the source files).

A traditional C compiler would only operate on a single source file per
run,
but like Microsoft's cl.exe, candle accepts multiple source files on the
same command line.

You should probably consider defining one Fragment per logical component
(not necessarily Component) of your product. Just like C# and C++
classes,
you can have more than one Fragment per source file, but it may be more
understandable if you stick to one Fragment per source file. Splitting
your
installation into more source files reduces the chance of checkout/merge
collisions with multiple developers.

In general, Fragments are much nicer to work with than merge modules.

-- 
Mike Dimmick

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Collins,
James
Sent: 25 July 2007 19:35
To: Bob Arnson; Jeroen Davelaar
Cc: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Msi inside msi ?

Hey Jeroen,

I'm also not sure what your trying to achieve however for me I
have very large installers including well over 16k files. For me I need
to split that up to reduce build time as well as keeping things modular.
The way I do that is with Merge Modules (MSM) which is basically an
installer inside an installer.

Jimbo

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, July 25, 2007 8:27 AM
To: Jeroen Davelaar
Cc: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Msi inside msi ?

Jeroen Davelaar wrote:
 How is it possible to nest a msi file with Orca while it is nog
possible to do the same thing with WiX? 
   

WiX deprecated the functionality when the MSI team deprecated it.

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



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users