date:20070529

Sign your MSI.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pseudonymic 
Wannabe
Sent: Tuesday, May 29, 2007 6:05 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Vista & unknown publisher

When running our MSI package on Vista midway under the installation a dialog 
pops up (UAC) and complains about "Unknown Publisher" on our package.MSI file 
and asks for permission to continue. Is there anyway to author our package in 
such a way that the user won't be bothered with such interference?

_
Like the way Microsoft Office Outlook works? You'll love Windows Live Hotmail.
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix Extension useable for 64 and 32 bit products

1.  No.  You can use 32-bit CustomActions in a 64-bit package.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cosmin Manoliu
Sent: Monday, May 28, 2007 12:13 AM
To: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix Extension useable for 64 and 32 bit products

Hello Rob,

Thank you for the answer.

1. I think I need to mark the MSI package as 64 bit. The reasons are: I
am doing COM registration, installation to 64 bit folders.
In this case probably I cannot go with 32 bit custom actions. Can you
please confirm?
The installer process will be a 64 bit process? In this case I guess is
not possible for it to call 32 bit custom actions.
I am not sure about this, the MSI documentation is not clear for me on
this issue.

2. I think I need to go with these option.
So far I successfully marshaled the other data to the compiler
(following the WiX CustomActions).
I don't know how can I marshal the Win64="yes" information to the
linker. Can you please point me to a sample
or documentation (or WiX source code)?
What means unreal table?

Rob Mensching wrote:
>
> 1. You do not have to provide CustomActions as both 64-bit and 32-bit.
> For example, all of the WiX CustomActions are 32-bit only and work
> fine on 64-bit machines.
>
> 2. If you want to switch between 64-bit and 32-bit (you can't have a
> package that installs both today) then you need to have some authoring
> (like Win64="yes") then marshal that data to your extension in the
> linker. An unreal table would probably be useful for that.
>
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] *On Behalf Of *Cosmin
> Manoliu
> *Sent:* Friday, May 25, 2007 4:15 AM
> *To:* WiX-users@lists.sourceforge.net
> *Subject:* [WiX-users] Wix Extension useable for 64 and 32 bit products
>
> Hello,
>
> I am using WiX 3. I am trying to develop a WiX extension for my custom
> actions.
> I follow the WiX Extension model.
>
> So far I did not found a good way to accomplish following: I would
> like to have the same
> WiX Extension use able on both 32 bit products and 64 bit products.
>
> As I understand it, I need to provide the custom action both as 64 bit
> build and 32 bit build,
> then I should write a WiX library which is scheduling the proper
> custom action.
> Following the WiX Extension model I should provide this library. All
> of these will happen at link time.
> As I see it, at link time, the information regarding MSI platform
> information is not available.
> These means that I only have the chance to write a proper WiX library
> which is able
> to schedule the correct custom action. Is this possible?
>
> am I missing something? Could you please point me to the right direction?
>
> Thanks
>

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to improve speed of installation?

2.  The files are installed in the order specified by the Sequence column.  The 
WiX toolset manages the Sequence column for you because the order should not 
matter.  The control you get is that you can control the order of groups of 
files because the Media element specify the order of each group.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Maslov
Sent: Friday, May 25, 2007 11:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?


> 2.  The cabinet is only opened once.  That's why the files have to be
sequenced perfectly because the
>  Windows Installer will only read through the File table sequentially and
> any files out of order will get
>  skipped.  Cabinet files are optimized for front to back reading not
> random access.


So does WiX sequence the files inside cabinets according to the Sequence
column of the File table?
Do I need to do anything special about that when I'm building install with
WiX?

I'm trying to layout cabinets and uncompressed files in the order they are
called, but
do I need to take special care of files inside cabinets, or WiX does it
automatically?

> 1.  Anti-virus software can cripple both the install time *and* the build
> time.
>  For build machines, you can usually tell the software to ignore the build
> directories and the temp
> directory.  For end user machines...

   Yes, I have anti virus, and can't switch it off - it policy.
   But when I look at CPU usage, it seems that anti-virus is only active for
part of the link process.





Rob Mensching-2 wrote:
>
> 1.  Anti-virus software can cripple both the install time *and* the build
> time.  For build machines, you can usually tell the software to ignore the
> build directories and the temp directory.  For end user machines...
> 
>
> 2.  The cabinet is only opened once.  That's why the files have to be
> sequenced perfectly because the Windows Installer will only read through
> the File table sequentially and any files out of order will get skipped.
> Cabinet files are optimized for front to back reading not random access.
>
> 3.  There is a cost of extracting embedded cabinets out of the MSI.
>
> 4.  There is some sweet spot for the size of cabinet files.  I remember
> hearing the Visual Studio guys playing with their cabinet composition
> trying to find the ideal size of the cabinets for decompression.  I don't
> remember the results, but it seemed like the ideal size of a cabinet was
> no larger than 200 MB with no more than a certain number of files...
> sorry, I don't remember more details.
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Friday, May 25, 2007 5:12 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] How to improve speed of installation?
>
> It may be a stupid question, but do you have any anti-virus software
> running? If so, that can completely cripple performance of an
> installation, and since you indicate that it is the "File copying" phase
> I would be interested to see what the difference is versus installing on
> a non-protected system.
>
> Rob M, can you (or anyone else with Microsoft Installer knowledge, or a
> communication channel to the developers) confirm if the cab files
> embedded in the installation are extracted from the MSI then opened
> once, or if the cab file is "reopened" for each file that is extracted
> from it. If it is the latter, it seems to me that multiple smaller cab
> files could provide significantly better performance than one large one
> if "on access" anti-virus scanning is enabled.
>
> Regards,
> Richard
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Igor
> Maslov
> Sent: Thursday, May 24, 2007 4:47 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] How to improve speed of installation?
>
>
>
> My "slow speed" comes from the "File copying" phase.
>
> I.e. all steps are running quite fast, but when I see "Copying Files" on
> a
> progress dialog
> it's where it takes most of the time.
>
>
>
> * 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.
> Peek 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 S

[WiX-users] Directory of US Realtors

2007-05-29 Thread Goldie acerbity




Brand New AMERICAN REAL ESTATE AGENTS Database

1,050,902 Total Records
85,658 Emails

Fresh data just compiled this week - never before sold. 

Regular price is $499

\
\\\SPECIAL PRICE UNTIL June 1st\\\
\\\ONLY $299!\\


For additional details or to purchase this database please 
send an email to: [EMAIL PROTECTED]










To cease future correspondence please reply with "777" in the subject heading

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to improve speed of installation?

[sorry, accidentally hit ctrl+enter]

1.  There is only a portion of light.exe that does major file IO.  If you 
cannot get an exception for some of your build drives with your antivirus 
software then you are going to be suffering with performance issues there.  
Seriously, I have seen 300% improvement in build times when people told their 
anti-virus programs to ignore the TEMP drive and build drive (YMMV depending on 
the anti-virus software you use).

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Tuesday, May 29, 2007 8:52 AM
To: Igor Maslov; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

2.  The files are installed in the order specified by the Sequence column.  The 
WiX toolset manages the Sequence column for you because the order should not 
matter.  The control you get is that you can control the order of groups of 
files because the Media element specify the order of each group.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Maslov
Sent: Friday, May 25, 2007 11:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?


> 2.  The cabinet is only opened once.  That's why the files have to be
sequenced perfectly because the
>  Windows Installer will only read through the File table sequentially and
> any files out of order will get
>  skipped.  Cabinet files are optimized for front to back reading not
> random access.


So does WiX sequence the files inside cabinets according to the Sequence
column of the File table?
Do I need to do anything special about that when I'm building install with
WiX?

I'm trying to layout cabinets and uncompressed files in the order they are
called, but
do I need to take special care of files inside cabinets, or WiX does it
automatically?

> 1.  Anti-virus software can cripple both the install time *and* the build
> time.
>  For build machines, you can usually tell the software to ignore the build
> directories and the temp
> directory.  For end user machines...

   Yes, I have anti virus, and can't switch it off - it policy.
   But when I look at CPU usage, it seems that anti-virus is only active for
part of the link process.





Rob Mensching-2 wrote:
>
> 1.  Anti-virus software can cripple both the install time *and* the build
> time.  For build machines, you can usually tell the software to ignore the
> build directories and the temp directory.  For end user machines...
> 
>
> 2.  The cabinet is only opened once.  That's why the files have to be
> sequenced perfectly because the Windows Installer will only read through
> the File table sequentially and any files out of order will get skipped.
> Cabinet files are optimized for front to back reading not random access.
>
> 3.  There is a cost of extracting embedded cabinets out of the MSI.
>
> 4.  There is some sweet spot for the size of cabinet files.  I remember
> hearing the Visual Studio guys playing with their cabinet composition
> trying to find the ideal size of the cabinets for decompression.  I don't
> remember the results, but it seemed like the ideal size of a cabinet was
> no larger than 200 MB with no more than a certain number of files...
> sorry, I don't remember more details.
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Friday, May 25, 2007 5:12 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] How to improve speed of installation?
>
> It may be a stupid question, but do you have any anti-virus software
> running? If so, that can completely cripple performance of an
> installation, and since you indicate that it is the "File copying" phase
> I would be interested to see what the difference is versus installing on
> a non-protected system.
>
> Rob M, can you (or anyone else with Microsoft Installer knowledge, or a
> communication channel to the developers) confirm if the cab files
> embedded in the installation are extracted from the MSI then opened
> once, or if the cab file is "reopened" for each file that is extracted
> from it. If it is the latter, it seems to me that multiple smaller cab
> files could provide significantly better performance than one large one
> if "on access" anti-virus scanning is enabled.
>
> Regards,
> Richard
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Igor
> Maslov
> Sent: Thursday, May 24, 2007 4:47 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] How to improve speed of installation?
>
>
>
> My "slow speed" comes from the "File copying" phase.
>
> I.e. all steps are running quite fast, but when I see "Copying Files" on
> a
> progress dialog
> it's where it takes most of the time.
>
>
>
> * C O N F I D E N T I A L I T Y N O T I C E *
> ---
> Th

Re: [WiX-users] How to improve speed of installation?

2.  15 minutes to copy 3-4 GB isn't bad too.  Remember, the WiX toolset is 
going to lay out your full DVD image in the way that the Windows Installer 
expects to see it.  Compression obviously takes more processing.  Also, with 
file IO much of the time will be counted against the operating system since so 
much time is going to be spent just pushing IO around at the lower levels of 
the operating system.  Light.exe is actually doing very little work.

On another thread, you mentioned you had a virus checker turned on that can 
actually greatly affect the performance.

Also, if the majority of your cabinets are the same, have you used the cabinet 
cache feature in the WiX toolset?  The cabinet cache checks to see that if a 
cabinet is already built it doesn't get created again.  If you haven't looked 
at this you really should (assuming you have some similar cabinets).

Finally, at a certain level, you're pushing (3 to 4) * N GB of data around in 
circles.  That simply takes time.  The only thing you can do is try to minimize 
the number of times you touch the files.  A more advanced series of steps could 
be to generate a .wixout, then use torch.exe to generate the transforms then 
build the .wixout into final .MSI packages.  That might not work out for the 
cases where files differ.

3.  Good, good, glad someone(s) here was able to help (wasn't me ).

4.  Indeed.  However, I'm used to fighting with QA where they argue for a 
robust install and I argue for a fast install.  Seems your QA team is on the 
other side this time.  

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Maslov
Sent: Friday, May 25, 2007 11:13 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

2. Candle is working fast enough.  It's light which is slow.

I switched off ICE validations (-sval). It helped a bit, but not
drammatically.

Linking  3-4 GB install takes 15 min if I don't compress data, and about
30-40 if I do compress data.
About 70% percent of the time I see that light takes only 3-4% of CPU.

   Light times aren't that bad when I do a single language. The problem for
me starts when I do
   multilanguage install. With multiple languages my approach maybe not
optimal, I know I could
   edit MSI tables very fast. But this is what I found I could do with with
Wix:

1. I create full install for neutral and each laguage.
2. Compute transforms between each language
3. Megre transforms into the base MSI

   In most setups, all the files that are installed are exactly the same for
different languages.
   Only installer dialogs differ.  In other installs, some installed files
differ, but majority is the same.

   Still looks like I have to create the full install, then compute
transforms.

   So , if a build for one language  completes in 30-40 min, then 5
languages + 1 neutral
   will take 3 -4 hours.   Not so nice anymore :)

   Yes, I can write my program to edit tables, to enter strings there, but
in case when not all files are
   language netral editing strings is not enough.

   Maybe there is a better approach than one that I used. I'd really
appreciate help here.

   PS. Building full installs for each language seems like a robust and
simple approach,
if only light were 4-5 times faster.

3. Intially speed was 300% up from my custom solution, but it seems I was
able to bring it
   down to more acceptable level. Thanks for help from this forum.

   Reducing number of components and laying out data on DVD - gives the
biggest boost.

4. Yes, but sometimes some of trade offs just aren't acceptable -  go, argue
with QA :)

Thanks,
Igor

Rob Mensching-2 wrote:
>
> 1.  Agreed.  I'm working on a more advanced chainer for the WiX toolset to
> hopefully ease a lot of this pain.  Just doesn't exist today.
>
> 2.  What was taking the majority of the build time?  Were you batching up
> your compiles (passing multiple .wxs files to candle.exe)?  Do you have
> shared cabinets, if so did you use the cabinet cache?  If you can provide
> some data about what is slow in the build times then there may be things
> that we can do to help (including potentially improving the WiX toolset).
>
> 3.  The Windows Installer does incur a bit of overhead because it tries
> harder for a "robust" install than a "fast" install.  Chances that the
> user will end up in a hosed state are far less with the Windows Installer
> (assuming no poor CustomActions).  The "robust" comes with some cost (like
> building the script for rollback).
>
> 4.  Tradeoffs?  Isn't this the way life works?  
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Igor Maslov
> Sent: Thursday, May 24, 2007 3:06 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] How to improve speed of installation?
>
>
> Yes,
>
> I'm asking myself whether it was a wise decision to move to MSI.
>
> It's not an

[WiX-users] Disabling features in the CustomizeDlg based on UI interaction...

2007-05-29 Thread Lewis Henderson

Hi All,

 

I'm still trying to port from InstallShield to wix, and here's the
problem I'm running into:  The user enters an authorization key, which
is checked for validity in a CA.  The CA also determines which features
are available based on this key, and I want to disable the features that
aren't available so they don't show up in the CustomizeDlg, which is
invoked shortly after the key is entered.  My CA is currently setting
property values for each feature to 0 or 1 and checked via Condition
clauses on the Feature declarations.  However, the conditions only
appear to be evaluated at compile file, not run time.

 

Can someone please either tell me how to make these conditions evaluate
after the CA is run, or point me to the right MSI routine call(s) to
reset the feature level to zero in my CA?  Thanks.

 

Lewis

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to improve speed of installation?

2007-05-29 Thread Pally Sandher

Couldn't one set the environment variable WIX_TEMP to somewhere in the
build area & therefore only have to exclude one area from AV on-demand
access?
I would personally be wary of excluding the entire TEMP directory,
whether it be on the user profile or the build machine's Windows
directory unless the build machine is used for nothing else at all in
which case why would AV be necessary in the first place on it?

Cheers,

Palbinder Sandher 
Software Deployment and
IT Administrator 

T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 
http://www.iesve.com 

**Design, Simulate + Innovate with the **

Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP

Email Disclaimer

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: 29 May 2007 16:55
To: Rob Mensching; Igor Maslov; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

[sorry, accidentally hit ctrl+enter]

1.  There is only a portion of light.exe that does major file IO.  If
you cannot get an exception for some of your build drives with your
antivirus software then you are going to be suffering with performance
issues there.  Seriously, I have seen 300% improvement in build times
when people told their anti-virus programs to ignore the TEMP drive and
build drive (YMMV depending on the anti-virus software you use).

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Tuesday, May 29, 2007 8:52 AM
To: Igor Maslov; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

2.  The files are installed in the order specified by the Sequence
column.  The WiX toolset manages the Sequence column for you because the
order should not matter.  The control you get is that you can control
the order of groups of files because the Media element specify the order
of each group.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Igor
Maslov
Sent: Friday, May 25, 2007 11:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

> 2.  The cabinet is only opened once.  That's why the files have to be
sequenced perfectly because the
>  Windows Installer will only read through the File table sequentially 
> and any files out of order will get  skipped.  Cabinet files are 
> optimized for front to back reading not random access.

So does WiX sequence the files inside cabinets according to the Sequence
column of the File table?
Do I need to do anything special about that when I'm building install
with WiX?

I'm trying to layout cabinets and uncompressed files in the order they
are called, but do I need to take special care of files inside cabinets,
or WiX does it automatically?

> 1.  Anti-virus software can cripple both the install time *and* the 
> build time.
>  For build machines, you can usually tell the software to ignore the 
> build directories and the temp directory.  For end user machines...

   Yes, I have anti virus, and can't switch it off - it policy.
   But when I look at CPU usage, it seems that anti-virus is only active
for part of the link process.

Rob Mensching-2 wrote:
>
> 1.  Anti-virus software can cripple both the install time *and* the 
> build time.  For build machines, you can usually tell the software to 
> ignore the build directories and the temp directory.  For end user
machines...
> 
>
> 2.  The cabinet is only opened once.  That's why the files have to be 
> sequenced perfectly because the Windows Installer will only read 
> through the File table sequentially and any files out of order will
get skipped.
> Cabinet files are optimized for front to back reading not random
access.
>
> 3.  There is a cost of extracting embedded cabinets out of the MSI.
>
> 4.  There is some sweet spot for the size of cabinet files.  I 
> remember hearing the Visual Studio guys playing with their cabinet 
> composition trying to find the ideal size of the cabinets for 
> decompression.  I don't remember the results, but it seemed like the 
> ideal size of a cabinet was no larger than 200 MB with no more than a
certain number of files...
> sorry, I don't remember more details.
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> [EMAIL PROTECTED]
> Sent: Friday, May 25, 2007 5:12 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] How to improve speed of installation?
>
> It may be a stupid question, but do you have any anti-virus software 
> running? If so, that can completely cripple performance of an 
> installation, and since you indicate that it is the "File copying" 
> phase I would be interested to see what the difference is versus 
> installing on a non-protected system.
>
> Rob M, can you (or anyone el

Re: [WiX-users] Disabling features in the CustomizeDlg based on UIinteraction...

2007-05-29 Thread Pally Sandher

I had a similar situation last week & recieved a grand total of 1
replies. I've come to the conclusion that using Condition to set the
Level of a Feature doesn't work (at all, as in it's a bug).
I tried to use it to set the Feature Level to either 1001 or 1 (1001
would exclude it from any install as my complete install has
SetInstallLevel of 1000). I also tried the 1/0 approach for
enable/disable as you have but no matter what I tried it never works as
like you I found it is never evaluated during the running of the
installer.
 
I had to use a Condition under a Component (which do appear to be
evaluated at install time) as all I wanted to do was make a single .ini
change based on a users choice. I don't think this will be sufficient
for what you're trying to do however.
 
A chap by the name of Don Tasanasanta suggested the following:
 
Have you tried using the commands:

 

Property=""


Property=""


 

The remove will disable a feature and the addlocal will enable a feature
when used with a control.

 
If you use your CustomAction to set a Property to "true" or "false" you
could something similar in the above code to enable/disable features
before a user chooses the type of install (as in the control which
publishes your equivalent of the SetupTypeDlg in WiXUI_Mondo).
 
I found something I thought might be useful called FeatureRequestState
on MSDN at http://msdn2.microsoft.com/en-us/library/aa371662.aspx but
since I'd solved the issue I was having I didn't investigate how to
implement it (if possible) in WiX. I think the above code would do a
similar if not the same thing however.
 
Cheers (and good luck),

  

Palbinder Sandher 
Software Deployment and
IT Administrator 

T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 
http://www.iesve.com  

**Design, Simulate + Innovate with the **

Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP

Email Disclaimer  















From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lewis
Henderson
Sent: 29 May 2007 17:20
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Disabling features in the CustomizeDlg based on
UIinteraction...



Hi All,

 

I'm still trying to port from InstallShield to wix, and here's the
problem I'm running into:  The user enters an authorization key, which
is checked for validity in a CA.  The CA also determines which features
are available based on this key, and I want to disable the features that
aren't available so they don't show up in the CustomizeDlg, which is
invoked shortly after the key is entered.  My CA is currently setting
property values for each feature to 0 or 1 and checked via Condition
clauses on the Feature declarations.  However, the conditions only
appear to be evaluated at compile file, not run time.

 

Can someone please either tell me how to make these conditions evaluate
after the CA is run, or point me to the right MSI routine call(s) to
reset the feature level to zero in my CA?  Thanks.

 

Lewis

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to improve speed of installation?

Yes, when I say temp directory, I mean wherever you have your temp directory 
pointing.  WIX_TEMP is a great way to use a custom temp location.

-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 9:30 AM
To: Rob Mensching; Igor Maslov
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] How to improve speed of installation?

Couldn't one set the environment variable WIX_TEMP to somewhere in the
build area & therefore only have to exclude one area from AV on-demand
access?
I would personally be wary of excluding the entire TEMP directory,
whether it be on the user profile or the build machine's Windows
directory unless the build machine is used for nothing else at all in
which case why would AV be necessary in the first place on it?

Cheers,

Palbinder Sandher
Software Deployment and
IT Administrator

T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com

**Design, Simulate + Innovate with the **

Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP

Email Disclaimer

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: 29 May 2007 16:55
To: Rob Mensching; Igor Maslov; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

[sorry, accidentally hit ctrl+enter]

1.  There is only a portion of light.exe that does major file IO.  If
you cannot get an exception for some of your build drives with your
antivirus software then you are going to be suffering with performance
issues there.  Seriously, I have seen 300% improvement in build times
when people told their anti-virus programs to ignore the TEMP drive and
build drive (YMMV depending on the anti-virus software you use).

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Tuesday, May 29, 2007 8:52 AM
To: Igor Maslov; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

2.  The files are installed in the order specified by the Sequence
column.  The WiX toolset manages the Sequence column for you because the
order should not matter.  The control you get is that you can control
the order of groups of files because the Media element specify the order
of each group.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Igor
Maslov
Sent: Friday, May 25, 2007 11:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to improve speed of installation?

> 2.  The cabinet is only opened once.  That's why the files have to be
sequenced perfectly because the
>  Windows Installer will only read through the File table sequentially
> and any files out of order will get  skipped.  Cabinet files are
> optimized for front to back reading not random access.

So does WiX sequence the files inside cabinets according to the Sequence
column of the File table?
Do I need to do anything special about that when I'm building install
with WiX?

I'm trying to layout cabinets and uncompressed files in the order they
are called, but do I need to take special care of files inside cabinets,
or WiX does it automatically?

> 1.  Anti-virus software can cripple both the install time *and* the
> build time.
>  For build machines, you can usually tell the software to ignore the
> build directories and the temp directory.  For end user machines...

   Yes, I have anti virus, and can't switch it off - it policy.
   But when I look at CPU usage, it seems that anti-virus is only active
for part of the link process.

Rob Mensching-2 wrote:
>
> 1.  Anti-virus software can cripple both the install time *and* the
> build time.  For build machines, you can usually tell the software to
> ignore the build directories and the temp directory.  For end user
machines...
> 
>
> 2.  The cabinet is only opened once.  That's why the files have to be
> sequenced perfectly because the Windows Installer will only read
> through the File table sequentially and any files out of order will
get skipped.
> Cabinet files are optimized for front to back reading not random
access.
>
> 3.  There is a cost of extracting embedded cabinets out of the MSI.
>
> 4.  There is some sweet spot for the size of cabinet files.  I
> remember hearing the Visual Studio guys playing with their cabinet
> composition trying to find the ideal size of the cabinets for
> decompression.  I don't remember the results, but it seemed like the
> ideal size of a cabinet was no larger than 200 MB with no more than a
certain number of files...
> sorry, I don't remember more details.
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Friday, May 25, 2007 5:12 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] How to improve speed

Re: [WiX-users] Vista & unknown publisher

2007-05-29 Thread Peterson, Joel

Just want to point out that even if you sign your MSI, you will still
get a "Unknown Publisher" on uninstallation.

It's sort of a sad limitation that is explained here:
http://blogs.msdn.com/windows_installer_team/archive/2006/10/19/new-wind
ows-installer-4-0-webcast-scheduled-and-q-a-from-lua-webcast.aspx

Question: When I uninstall my signed msi, I get a UAC prompt that says
"Unknown publisher". All of the UAC prompts during the install display
my signed information fine. Is this a Vista problem, or a problem with
my msi.

Answer: We have a KB pending for this behavior and are considering this
for a fix. The reason this happens is that when we cache the MSI we
strip out some data, making the certificate invalid. We're looking at
mitigations but we do not have a solution at this time. Nothing is wrong
with the package.

Joel Peterson
Quality Engineer
[EMAIL PROTECTED]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Tuesday, May 29, 2007 8:47 AM
To: Pseudonymic Wannabe; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Vista & unknown publisher

Sign your MSI.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Pseudonymic Wannabe
Sent: Tuesday, May 29, 2007 6:05 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Vista & unknown publisher

When running our MSI package on Vista midway under the installation a
dialog pops up (UAC) and complains about "Unknown Publisher" on our
package.MSI file and asks for permission to continue. Is there anyway to
author our package in such a way that the user won't be bothered with
such interference?

_
Like the way Microsoft Office Outlook works? You'll love Windows Live
Hotmail.
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migr
ation_HM_mini_outlook_0507




-
This SF.net email is sponsored by DB2 Express Download DB2 Express C -
the FREE version of DB2 express and take control of your XML. No limits.
Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Control-condition for install-only

Pseudonymic Wannabe wrote:
> For our installation we have a lot of custom actions being called, all 
> the post-install ones are chain-schedualed after InstallFinalize

As an aside: That's outside the install transaction, so you can leave 
the machine in a bad state if any custom action fails.

> NOT INSTALLED AND NOT REINSTALL does NOT seem to work for a "Show", IF 
> condition for a control on the ExitDialog page though (The same 
> exit-dialog page is shown for install, repair and uninstall). We want 
> to show a checkbox for application-launch, which of course should only 
> show on fresh install.

Is that a literal? The actual property is Installed not INSTALLED. 
Here's what WixUI uses for the same type of checkbox:

WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT AND 
NOT Installed

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

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX and string formatting


[EMAIL PROTECTED] wrote:


It was my understanding that formatted text expansion would typically 
occur before the user interface is shown. In this specific case, the 
user conducting the installation will be modifying the values, hence 
the reason why I (and apparently Rennie also) believed a custom action 
would be required. Are you saying that formatted text fields (where 
supported) are always re-evaluated before use?




Formatted text is evaluated at time of use wherever MSI lists a column 
as being formatted or supporting formatted text. Some formatting is only 
valid at certain times or under certain conditions (e.g., [#fileId] or 
[$componentId]). But it does require an explicit evaluation call so if 
it's not documented as being formatted, it won't work (e.g., inside an 
RTF control).


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

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Help with Properties set in a UI then used in a Custom Action

Rik wrote:
> I am creating an installer that has a UI that allows the user to enter 
> some values.  These values are subsequently used in a custom action as 
> part of the actual installation.  

Properties must be public (i.e., named in all UPPERCASE) and secure 
(@Secure="yes") to be passed from the UI sequence to the execute sequence.

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

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Connecting many files to a single component

hariom wrote:
> directory. That means for example I can select only *.aspx files OR *.dll
> from particular directory. Is that this feature is available in WIX also?
>   

No. It's been discussed on the list many times (search the archives for 
the fun). You can use the heat tool in WiX v3 or tallow in WiX v2 to do 
a one-time generation.

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

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Disabling features in the CustomizeDlg based on UIinteraction...


I use this very successfully actually and have not had any problems with
it.  My feature declaration looks like this:

  
  
  


The "Condition" tag sets the feature to 1 or 0 based on the presence of
[MY_NEEDED_PROPERTY].  I use this in several different installs and it works
great.  For instance I have an install where the client and server
components are in the same install and you can't install both on the same
box.  That is where this example comes from as a matter of fact.  You could
go even further to place conditions on the individual components that check
for the install actions of particular features to ensure the desired
installation behavior.

See the following for more information:
http://msdn2.microsoft.com/en-us/library/aa368014.aspx
http://msdn2.microsoft.com/en-us/library/aa368012.aspx

Regards,
//aj

On 5/29/07, Pally Sandher <[EMAIL PROTECTED]> wrote:


 I had a similar situation last week & recieved a grand total of 1
replies. I've come to the conclusion that using Condition to set the Level
of a Feature doesn't work (at all, as in it's a bug).
I tried to use it to set the Feature Level to either 1001 or 1 (1001 would
exclude it from any install as my complete install has SetInstallLevel of
1000). I also tried the 1/0 approach for enable/disable as you have but no
matter what I tried it never works as like you I found it is never evaluated
during the running of the installer.

I had to use a Condition under a Component (which do appear to be
evaluated at install time) as all I wanted to do was make a single .ini
change based on a users choice. I don't think this will be sufficient for
what you're trying to do however.

A chap by the name of Don Tasanasanta suggested the following:


Have you tried using the commands:



Property=""


Property=""




The remove will disable a feature and the addlocal will enable a feature
when used with a control.

If you use your CustomAction to set a Property to "true" or "false" you
could something similar in the above code to enable/disable features before
a user chooses the type of install (as in the control which publishes your
equivalent of the SetupTypeDlg in WiXUI_Mondo).

I found something I thought might be useful called FeatureRequestState on
MSDN at http://msdn2.microsoft.com/en-us/library/aa371662.aspx but since
I'd solved the issue I was having I didn't investigate how to implement it
(if possible) in WiX. I think the above code would do a similar if not the
same thing however.

Cheers (and good luck),

 

*Palbinder Sandher
Software Deployment and
IT Administrator *

T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com

**Design, Simulate + Innovate with the **

Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP

Email Disclaimer 










 --
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Lewis Henderson
*Sent:* 29 May 2007 17:20
*To:* wix-users@lists.sourceforge.net
*Subject:* [WiX-users] Disabling features in the CustomizeDlg based on
UIinteraction...

 Hi All,



I'm still trying to port from InstallShield to wix, and here's the problem
I'm running into:  The user enters an authorization key, which is checked
for validity in a CA.  The CA also determines which features are available
based on this key, and I want to disable the features that aren't available
so they don't show up in the CustomizeDlg, which is invoked shortly after
the key is entered.  My CA is currently setting property values for each
feature to 0 or 1 and checked via Condition clauses on the Feature
declarations.  However, the conditions only appear to be evaluated at
compile file, not run time.



Can someone please either tell me how to make these conditions evaluate
after the CA is run, or point me to the right MSI routine call(s) to reset
the feature level to zero in my CA?  Thanks.



Lewis

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Connecting many files to a single component

You can do it, but not in the way you describe.

...

This will group several files into one component, but you can not use a
wildcard reference on a directory. Heat works *okay*, but I don't like the
output so I usually end up changing it around a bit. The -gg option won't
show up in the command line help for heat, but you may want to use it on a
first-time basis to generate the GUIDs for you when creating the initial
references to your files.

Regards,
//aj

On 5/29/07, hariom <[EMAIL PROTECTED]> wrote:

Hi All,

I am a newbie to WIX, but I am using Installshield. Now I need to port my
installers to WIX. In Installshield while doing Dynamic File Linking
option
I will be getting a option like, I can select only required files from
that
directory. That means for example I can select only *.aspx files OR *.dll
from particular directory. Is that this feature is available in WIX also?

Let me put my question in this way also, can I connect multiple files to a
single compoent?

If I am trying to use this light.exe is throwing error.

Please help me and thanks in advance :)
--
View this message in context:
http://www.nabble.com/Connecting-many-files-to-a-single-component-tf3834116.html#a10854708
Sent from the wix-users mailing list archive at Nabble.com.

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] error dialog issue

2007-05-29 Thread Nitin Chaudhari


Hi,

My Error Dialog is as follows:

 

   

 

   

   

   

   

 

   

   

 

 

   

 

Although the Pushbutton is place at X=278 and the form is of width
370, it still appears center of the dialog (screenshot attached). How
can I place it at the co-ordinates I want?

Also, the installation starts with the Installing dialog (from
InstallUISequence) and then I get this error dialog
(CA_ErrExcelNotInstalled from InstallExecuteSequence).

How can I sync these two? Now the situation is that I have 2 msiexec
process running on my machine, and when I click "Finish" – for error
dialog, 1 msiexec proc ends, but the other stays, and sometimes I get
a msg saying that an installation is in progress.


I want to execute the custom actions and then if they don't return
error, I want to start with the installing dialog.

I don't want to use launch conditions coz I read somewhere that they
cause issues sometimes.

Installexecutesequence and install UI sequence tags are as follows:



 

 

 

 

 

 

   



 

   

   

   

   

   

   

   

 


Thanks,
Nitin
<>-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Disabling features in the CustomizeDlg based on UI interaction...

2007-05-29 Thread Lewis Henderson

Hi All,

Thanks for the reply, but that doesn't do it for me.  If I use this
code, all of the features are disabled since none of the property values
are set initially.  As a reminder, I set property values in a CA called
from a UI before the CustomizeDlg is called.  Since I can't seem to
Feature conditions to evaluate at the time of the CustomizeDlg call, is
there some MSI function I can call from C in my UI that can set the
Feature Level in the database?

Lewis

-Original Message-
>Date: Tue, 29 May 2007 11:01:13 -0700
>From: "Aaron Shurts" <[EMAIL PROTECTED]>
>Subject: Re: [WiX-users] Disabling features in the CustomizeDlg based>
>   on  UIinteraction...
>To: "Pally Sandher" <[EMAIL PROTECTED]>
>Cc: Lewis Henderson <[EMAIL PROTECTED]>,
>   wix-users@lists.sourceforge.net
>Message-ID:
>   <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset="iso-8859-1"
>
>I use this very successfully actually and have not had any problems
with
>it.  My feature declaration looks like this:
>Level="1" ConfigurableDirectory="INSTALLDIR" AllowAdvertise="no">
>   
>   
>   
>
>
>The "Condition" tag sets the feature to 1 or 0 based on the presence of
>[MY_NEEDED_PROPERTY].  I use this in several different installs and it
>works
>great.  For instance I have an install where the client and server
>components are in the same install and you can't install both on the
same
>box.  That is where this example comes from as a matter of fact.  You
could
>go even further to place conditions on the individual components that
check
>for the install actions of particular features to ensure the desired
>installation behavior.
>
>See the following for more information:
>http://msdn2.microsoft.com/en-us/library/aa368014.aspx
>http://msdn2.microsoft.com/en-us/library/aa368012.aspx
>
>Regards,
>//aj


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Help with Properties set in a UI then used in a Custom Action

2007-05-29 Thread Rik

That fixed it, thanks Bob.

As a comment:
Isn't it unusual convention to have the case of a name dictating the
protection level?  I guess that's a legacy thing from MSI, rather than a
feature of WiX..?

On 29/05/07, Bob Arnson <[EMAIL PROTECTED]> wrote:

Rik wrote:
> I am creating an installer that has a UI that allows the user to enter
> some values.  These values are subsequently used in a custom action as
> part of the actual installation.

Properties must be public (i.e., named in all UPPERCASE) and secure
(@Secure="yes") to be passed from the UI sequence to the execute sequence.

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

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Fwd: Connecting many files to a single component

2007-05-29 Thread Rik


I might have sent my reply to the wrong address earlier.  Apologies if it
double-posts...


 Hi hariom,

I'm using WiX v2.0.
I managed to achieve what you're looking for by using tallow.exe with
msbuild.  In fact I wrote a custom task that calls the tallow executable and
parses and re-formats the results.  The parameters of the custom action were
the search path ( e.g. C:\source\debug\*.dll) and the name of the file to
output the results to.  The msbuild script then included the my main wix
file plus anything created by Tallow, and hands it over to wix to be
packaged into an MSI.

It took a bit of sorting out, but it works very well indeed.

Rik


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]>]
On Behalf Of hariom
Sent: 29 May 2007 15:04
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Connecting many files to a single component

Hi All,

I am a newbie to WIX, but I am using Installshield. Now I need to port my
installers to WIX. In Installshield while doing Dynamic File Linking option
I will be getting a option like, I can select only required files from that
directory. That means for example I can select only *.aspx files OR *.dll
from particular directory. Is that this feature is available in WIX also?

Let me put my question in this way also, can I connect multiple files to a
single compoent?

 If I am trying to use this light.exe is throwing error.

Please help me and thanks in advance :)
--

Sent from the wix-users mailing list archive at Nabble.com.

-
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the
FREE version of DB2 express and take control of your XML. No limits. Just
data. Click to get it now.

http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

REED ELSEVIER (UK) LIMITED - Registered office - 1-3 STRAND, LONDON WC2N 5JR
Registered in England - Company No. 02746621

Reed Elsevier (UK) Ltd - Registered in England Number 2746621 - Registered
Office 1 - 3 Strand, London WC2N 5JR
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] - Changing "OK" button to "Close" button.

2007-05-29 Thread Sankaranarayanan

Hi,

I got the desired effect by including the contents of ErrorDlg.wxs file in my 
WXS file and modifying the Text attribute as follows

Please let me know if this approach is a good practice.

Thanks,
Sankaranarayanan MG

- Original Message 
From: Bob Arnson <[EMAIL PROTECTED]>
To: Sankaranarayanan <[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net
Sent: Monday, 28 May, 2007 2:28:00 PM
Subject: Re: [WiX-users]  - Changing "OK" button to "Close" 
button.

Sankaranarayanan wrote:
> I want the button text to read "Close" instead of "OK". Which dialog.wxs file 
> needs to be changed for obtaining this bahavior.
>   

Launch conditions are processed by the LaunchConditions standard action. 
It controls the UI and offers no customization. If you want a different 
UI, you need to author it yourself and use type 19 custom actions to 
cancel the installation.

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

  ___
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/ 

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Disabling features in the CustomizeDlg based on UI interaction...

You may be able to build your ADDLOCAL property from checkboxes instead of
using the Feature Selection dialog.  This would allow you to enable or
disable the checkboxes based on property values.

The problem you are having is a sequencing problem.  The feature conditions
have already been evaluated by the time your custom action runs.  Thusly,
manipulating what the user can and cannot select is a difficult task.

You are running in to what happens to be one of the biggest complaints about
Windows Installer, the UI.  To really have full control over it, you'll need
to write your own UI.

...which is not as difficult or lengthy as it might sound.  There are a
plethora of topics in the SDK that cover how to do this, see the following
topic for example:
http://msdn2.microsoft.com/en-us/library/aa369544.aspx

Regards,
//aj

On 5/29/07, Lewis Henderson <[EMAIL PROTECTED]> wrote:

Hi All,

Thanks for the reply, but that doesn't do it for me.  If I use this
code, all of the features are disabled since none of the property values
are set initially.  As a reminder, I set property values in a CA called
from a UI before the CustomizeDlg is called.  Since I can't seem to
Feature conditions to evaluate at the time of the CustomizeDlg call, is
there some MSI function I can call from C in my UI that can set the
Feature Level in the database?

Lewis

-Original Message-
>Date: Tue, 29 May 2007 11:01:13 -0700
>From: "Aaron Shurts" <[EMAIL PROTECTED]>
>Subject: Re: [WiX-users] Disabling features in the CustomizeDlg based>
>   on  UIinteraction...
>To: "Pally Sandher" <[EMAIL PROTECTED]>
>Cc: Lewis Henderson <[EMAIL PROTECTED]>,
>   wix-users@lists.sourceforge.net
>Message-ID:
>   <[EMAIL PROTECTED]>
>Content-Type: text/plain; charset="iso-8859-1"
>
>I use this very successfully actually and have not had any problems
with
>it.  My feature declaration looks like this:
>Level="1" ConfigurableDirectory="INSTALLDIR" AllowAdvertise="no">
>   
>   
>   
>
>
>The "Condition" tag sets the feature to 1 or 0 based on the presence of
>[MY_NEEDED_PROPERTY].  I use this in several different installs and it
>works
>great.  For instance I have an install where the client and server
>components are in the same install and you can't install both on the
same
>box.  That is where this example comes from as a matter of fact.  You
could
>go even further to place conditions on the individual components that
check
>for the install actions of particular features to ensure the desired
>installation behavior.
>
>See the following for more information:
>http://msdn2.microsoft.com/en-us/library/aa368014.aspx
>http://msdn2.microsoft.com/en-us/library/aa368012.aspx
>
>Regards,
>//aj

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Help with Properties set in a UI then used in a Custom Action

Yeah, it's an MSI thing.  Goofy?  Agreed.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rik
Sent: Tuesday, May 29, 2007 12:25 PM
To: Bob Arnson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Help with Properties set in a UI then used in a Custom 
Action

That fixed it, thanks Bob.

As a comment:
Isn't it unusual convention to have the case of a name dictating the protection 
level?  I guess that's a legacy thing from MSI, rather than a feature of WiX..?
On 29/05/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Rik wrote:
> I am creating an installer that has a UI that allows the user to enter
> some values.  These values are subsequently used in a custom action as
> part of the actual installation.

Properties must be public ( i.e., named in all UPPERCASE) and secure
(@Secure="yes") to be passed from the UI sequence to the execute sequence.

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

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Votive under VS2005 reports "This installation is forbidden by system policy" when running as LUA

2007-05-29 Thread Ben Day


I've got the same error trying to build my WiX (Votive) setup project as part
of my Team Build.  

"light.exe(0,0): error LGHT0216: An unexpected Win32 exception with error
code 0x659 occurred: This installation is forbidden by system policy. 
Contact your system administrator."

The project builds fine if I run a desktop build and through VS2005.  

I've tried adding the DisableMSI registry key and setting the value to "0"
and still no luck.  I'm ready to disable validation -- problem is, I don't
know how to do it.

Using Votive (5/25/2007 release), how do I specify "-sval"?   

Thanks,

-Ben Day
Microsoft MVP for C#




Rob Mensching-2 wrote:
> 
> Validation (which is executed by default) starts up the Windows Installer
> engine.  If you have the Windows Installer engine disabled, validation
> will always fail.  You'd want to suppress validation (-sval) or allow the
> Windows Installer engine to run.  Of course, validation can catch some
> errors in your MSI so I recommend leaving it on.
> 
> "Mangaged" in this case means "administrator said it was okay to run this
> MSI on your machine".
> 
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Roger
> Lipscombe
> Sent: Thursday, February 08, 2007 4:28 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Votive under VS2005 reports "This installation is
> forbidden by system policy" when running as LUA
> 
> [Please excuse me if this is a stupid question: I'm just getting started
> with WiX]
> 
> I'm just playing with WiX v3.0 and Votive. I've created a new WiX MSI
> project, and when building it (and changing all the PUT-WHATEVER-HERE
> values), Light reports the following error:
> 
> Error LGHT0216: An unexpected Win32 exception with error code 0x659
> occurred: This installation is forbidden by system policy.  Contact your
> system administrator
> 
> I looked this up in Google, and all I could find were references to the
> HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer, specifically the
> DisableMSI value (documented at
> http://msdn2.microsoft.com/en-us/library/aa368304.aspx). I'm running
> Windows 2003, so I guess that the default applies. I assume that "managed
> applications" in this context means .NET applications, correct?
> 
> When I build it with an admin account, I get an ICE validation error
> instead. It appears to me that the ICE checks don't work in a non-Admin
> account. Is there any way to get them to work, or should I simply turn
> them off? If I turn them off, then the project builds successfully, but
> this probably isn't ideal.
> 
> I'd prefer not to set DisableMSI to zero, which appears to allow
> installations for all applications, because I think that it might open a
> security hole. Or am I missing something?
> 
> Regards,
> Roger.
> 
> 
> 
> 
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind 1E Ltd to any order or other contract unless pursuant to explicit
> written agreement or government initiative expressly permitting the use of
> e-mail for such purpose.
> 
> 
> 
> -
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> ___
> 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/Votive-under-VS2005-reports-%22This-installation-is-forbidden-by-system-policy%22-when-running-as-LUA-tf3193035.html#a10862389
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Votive under VS2005 reports "This installation is forbidden by system policy" when running as LUA

2007-05-29 Thread Ben Day


I figured out how to specify "-sval" using Votive.

0. Check out your Votive setup project from source control
1. Right click on your Votive setup project
2. Click on Linker
3. Select the "Configuration" for which you want to specify -sval
4. Click "Advanced..."
5. On the "Light Advanced Settings" dialog, click the "Suppressions" tab
6. Check "Supress MSI/MSM validation"
7. Click OK
8. Save the file (CTRL-S)

This fixed my immediate LGHT0216 error but I'd still like to solve the
underlying issue.

Thanks,
-Ben



Ben Day wrote:
> 
> I've got the same error trying to build my WiX (Votive) setup project as
> part of my Team Build.  
> 
> "light.exe(0,0): error LGHT0216: An unexpected Win32 exception with error
> code 0x659 occurred: This installation is forbidden by system policy. 
> Contact your system administrator."
> 
> The project builds fine if I run a desktop build and through VS2005.  
> 
> I've tried adding the DisableMSI registry key and setting the value to "0"
> and still no luck.  I'm ready to disable validation -- problem is, I don't
> know how to do it.
> 
> Using Votive (5/25/2007 release), how do I specify "-sval"?   
> 
> Thanks,
> 
> -Ben Day
> Microsoft MVP for C#
> 
> 
> 
> 
> Rob Mensching-2 wrote:
>> 
>> Validation (which is executed by default) starts up the Windows Installer
>> engine.  If you have the Windows Installer engine disabled, validation
>> will always fail.  You'd want to suppress validation (-sval) or allow the
>> Windows Installer engine to run.  Of course, validation can catch some
>> errors in your MSI so I recommend leaving it on.
>> 
>> "Mangaged" in this case means "administrator said it was okay to run this
>> MSI on your machine".
>> 
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Roger
>> Lipscombe
>> Sent: Thursday, February 08, 2007 4:28 AM
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] Votive under VS2005 reports "This installation is
>> forbidden by system policy" when running as LUA
>> 
>> [Please excuse me if this is a stupid question: I'm just getting started
>> with WiX]
>> 
>> I'm just playing with WiX v3.0 and Votive. I've created a new WiX MSI
>> project, and when building it (and changing all the PUT-WHATEVER-HERE
>> values), Light reports the following error:
>> 
>> Error LGHT0216: An unexpected Win32 exception with error code 0x659
>> occurred: This installation is forbidden by system policy.  Contact your
>> system administrator
>> 
>> I looked this up in Google, and all I could find were references to the
>> HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer, specifically the
>> DisableMSI value (documented at
>> http://msdn2.microsoft.com/en-us/library/aa368304.aspx). I'm running
>> Windows 2003, so I guess that the default applies. I assume that "managed
>> applications" in this context means .NET applications, correct?
>> 
>> When I build it with an admin account, I get an ICE validation error
>> instead. It appears to me that the ICE checks don't work in a non-Admin
>> account. Is there any way to get them to work, or should I simply turn
>> them off? If I turn them off, then the project builds successfully, but
>> this probably isn't ideal.
>> 
>> I'd prefer not to set DisableMSI to zero, which appears to allow
>> installations for all applications, because I think that it might open a
>> security hole. Or am I missing something?
>> 
>> Regards,
>> Roger.
>> 
>> 
>> 
>> 
>> This is a PRIVATE message. If you are not the intended recipient, please
>> delete without copying and kindly advise us by e-mail of the mistake in
>> delivery. NOTE: Regardless of content, this e-mail shall not operate to
>> bind 1E Ltd to any order or other contract unless pursuant to explicit
>> written agreement or government initiative expressly permitting the use
>> of e-mail for such purpose.
>> 
>> 
>> 
>> -
>> Using Tomcat but need to do more? Need to support web services, security?
>> Get stuff done quickly with pre-integrated technology to make your job
>> easier.
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> ___
>> 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/Votive-under-VS2005-reports-%22This-installation-is-forbidden-by-system-policy%22-when-running-as-LUA-tf3193035.html#a10862713
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C

[WiX-users] Can someone provide some direction on using the NAnt tasks to build for WiX v3?