Quantcast

help: unsubscribe

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

help: unsubscribe

Murtaza Chowdhury


-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
Sent: 02 September 2010 19:21
To: [hidden email]
Subject: WiX-users Digest, Vol 52, Issue 6

Send WiX-users mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific than "Re: Contents of WiX-users digest..."


Today's Topics:

   1. Re: wix shortcut "run as administrator". (MYFLEX)
   2. Re: Wix 3.0 Source Code (Bob Arnson)
   3. Re: Bootstrapping and Burn (Bob Arnson)
   4. Re: missing wcautil.lib for ia64 platform (Bob Arnson)
   5. Re: Are there nl-nl localizations available for the wix
      extensions? (Bob Arnson)
   6. Re: Preprocessor Extension question (Bob Arnson)
   7. Re: Newbie x64 msi question (Bob Arnson)
   8. Re: CustomAction stored in Property (Bob Arnson)
   9. Re: Browse location fails if current install location is an
      empty CD drive. (Bob Arnson)
  10. Re: Wix properties not being persisted from a WXI (<Control>)
      to a WXS (<InstallExecuteSequence>) (Bob Arnson)


----------------------------------------------------------------------

Message: 1
Date: Thu, 2 Sep 2010 05:06:36 -0700 (PDT)
From: MYFLEX <[hidden email]>
Subject: Re: [WiX-users] wix shortcut "run as administrator".
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii


Hi phil,

If I set Advertise="No" it is giving the following error.


Error 71 ICE43: Component aa has non-advertised shortcuts. It should use a
registry key under HKCU as its KeyPath, not a file.
Error 72 ICE57: Component 'SHORT' has both per-user and per-machine data
with a per-machine KeyPath.

Please tell me how to fix those errors.
       

--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix-shortcut-run-as-administrator-tp5443294p5490855.html
Sent from the wix-users mailing list archive at Nabble.com.



------------------------------

Message: 2
Date: Thu, 02 Sep 2010 08:32:33 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] Wix 3.0 Source Code
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 02-Sep-10 06:10, Satyaprakash J wrote:
>                  I would like to know from where I can download the source code for Wix 3.0 .  The links on the web seem to be broken.

Which links?

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




------------------------------

Message: 3
Date: Thu, 02 Sep 2010 08:32:20 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] Bootstrapping and Burn
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 02-Sep-10 06:13, Pally Sandher wrote:
> I have personally fixed things like that myself. Last year one of our dev's decided to implement the use of CAPICOM for some basic password encryption&  MD5 checking&  thought it was OK to tell me "just self-register the CAPICOM DLL in the installer&  it'll work". He was also recommending we use an out-dated version of the discontinued CAPICOM containing some known security vulnerabilities. I re-wrote his code using the CryptoAPI completely removing the need for the CAPICOM redistributable. Incidentally he no longer works for us any more.
>
> When the product developers make stupid decisions which impact upon setup development, call them on it or be prepared to put up with more of the same until the end of time.

This is why it's important for "setup developers" to be developers in
their own right, so they can speak with authority and, when necessary,
write code outside of setup to "lend a hand."

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




------------------------------

Message: 4
Date: Thu, 02 Sep 2010 08:34:14 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] missing wcautil.lib for ia64 platform
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 02-Sep-10 06:03, [hidden email] wrote:
> I have the following question: why there is no version of wcautil
> library for ia64 platform in wix SDK?

Probably because nobody noticed or complained: IA64 isn't exactly a
popular platform nor is it gaining in popularity. Feel free to enter a
bug but you might also want to just build it yourself.

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




------------------------------

Message: 5
Date: Thu, 02 Sep 2010 08:36:39 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] Are there nl-nl localizations available for
        the wix extensions?
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 01-Sep-10 03:38, Valentijn Makkenze wrote:
> I'm using Wix 3.5.2020 and the WixIIsExtension and WixUtilExtension

No, nobody's contributed localizations for nl-NL for those extensions.

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




------------------------------

Message: 6
Date: Thu, 02 Sep 2010 08:37:51 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] Preprocessor Extension question
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 31-Aug-10 13:41, Maillet, Ed wrote:
> The Preprocessor.GetSourceLineNumbers doesn't work because the preprocessor extension doesn't get the XmlNode. (Or it's hiding somewhere I haven't seen).

Please enter a bug to have it exposed.

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




------------------------------

Message: 7
Date: Thu, 02 Sep 2010 08:40:48 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] Newbie x64 msi question
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 30-Aug-10 01:36, Andres Juarez wrote:
> So, running candle with teh -arch switch does take care of marking the
> components at 64 bits, but if using the same Wix source file for the
> 32 and 64 bits installer with the only difference of the candle -arh
> switch, the Components GUIDS for the 64 and 32 bits installer are all
> the same.

If you use "*" component guids, they'll be different based on the root
directory.

> The two installers cannot install in the same box since the launch
> conditios are mutually exclusive. Do we still need to have unique
> GUIDS per components, I am almost sure we do, but just asking.

No. If the packages are mutually exclusive, you'll never run into a
problem. And even if they did both install on the same machine, it's
legal to have the same component in multiple products, as long as the
components have identical composition.

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




------------------------------

Message: 8
Date: Thu, 02 Sep 2010 08:57:13 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] CustomAction stored in Property
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 30-Aug-10 12:41, [hidden email] wrote:
> Of course, there is no custom action "[CustomSerialValidateProp]". But property CustomSerialValidateProp contains actual custom action.

As in VBScript or JScript? It looks like that's not supported. Feel free
to file a bug -- and get rid of your dependence on script:
http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx

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




------------------------------

Message: 9
Date: Thu, 02 Sep 2010 09:01:05 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] Browse location fails if current install
        location is an empty CD drive.
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 30-Aug-10 10:12, Christopher Hughes wrote:
> I've looked at the log file (using /lv) but can't quite see which dlg the error originates from. I looked up WixUIValidatePath you mentioned and tried adding the following property to supprress it, but to no avail:
>
> <Property Id="WIXUI_DONTVALIDATEPATH" Value="1"/>

Then it's not WiX throwing the error but MSI. I'm guessing MSI's tree
control doesn't like the hard-coded drive letter that it can't use. Does
it work if you run a silent install? You might need a different approach.

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




------------------------------

Message: 10
Date: Thu, 02 Sep 2010 09:01:48 -0400
From: Bob Arnson <[hidden email]>
Subject: Re: [WiX-users] Wix properties not being persisted from a WXI
        (<Control>) to a WXS (<InstallExecuteSequence>)
To: [hidden email]
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

  On 28-Aug-10 14:40, Rafael Campana wrote:
> <Property Id='MYPROPERTY'>1</Property>

Properties must be marked Secure="yes" to be used from both UI and
execute sequences.

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




------------------------------

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd

------------------------------

_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users


End of WiX-users Digest, Vol 52, Issue 6
****************************************


------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: help: unsubscribe

Blair Murri-3
As the instructions say: send an email with "help" in the subject line to:
[hidden email] and the list-service will reply with
instructions to unsubscribe.

Don't send the message to the wix-users list. No one here can easily help
you.

-----Original Message-----
From: Murtaza Chowdhury [mailto:[hidden email]]
Sent: Thursday, September 02, 2010 7:00 AM
To: [hidden email]
Subject: [WiX-users] help: unsubscribe



-----Original Message-----
From: [hidden email]
[mailto:[hidden email]]
Sent: 02 September 2010 19:21
To: [hidden email]
Subject: WiX-users Digest, Vol 52, Issue 6

Send WiX-users mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]



------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Loading...