[mailto:[EMAIL PROTECTED] On Behalf Of André Pönitz
Sent: 20 December 2006 15:00
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Trouble with Shortcuts...
Mike Dimmick wrote:
> If you don't think you need install-on-demand,
> repair-on-launch, or the ability for domain administ
Mike Dimmick wrote:
> If you don't think you need install-on-demand,
> repair-on-launch, or the ability for domain administrators to
> advertise software through Group Policy, by all means use
> non-advertised shortcuts.
Which, unfortunately, does not seem to work with Wix v3 and
validation. At
-users@lists.sourceforge.net
Subject: Re: [WiX-users] Trouble with Shortcuts...
I'm afraid you generated more questions :) ...
On 12/18/06, Mike Dimmick <[EMAIL PROTECTED]> wrote:
An advertised shortcut goes through the Windows Installer engine
rather than running the p
I'm afraid you generated more questions :) ...
On 12/18/06, Mike Dimmick <[EMAIL PROTECTED]> wrote:
An advertised shortcut goes through the Windows Installer engine rather
than running the program (or document) directly. This enables Windows
Installer to check that all components of the requir
TECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: 18 December 2006 22:46
To: Wilson, Phil
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Trouble with Shortcuts...
When I made my installer with WiX was the first time I had ever seen the
greyed out target. Everyone in th
When I made my installer with WiX was the first time I had ever seen the
greyed out target. Everyone in the office that I mentioned it to indicated
that it was new to them I don't use MS Office, and the Office users around
here weren't familiar with them. So they may have used them, but they
di
OT of people have
used them and seen them!
Phil Wilson
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Monday, December 18, 2006 6:44 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Trouble with Shor
Creating a shortcut shouldn't be a "complication". Until I did my installer
with WiX nobody in the company had ever seen an "advertised" shortcut...
only a couple of them had even heard of them. Nobody actually wants them,
but I was forced to use them for the same reason, to avoid the complicati
André Pönitz wrote:
> The current behaviour certainly makes sense from a purely technical
> point of view. However, in practise one seemingly has to disable
> (some) ICEs just to get some of the most common features compiled.
> So the 'default' ICEing is far less useful than it might be.
>
Sorr
Bob Arnson wrote:
> Scott Palmer wrote:
> > Then I get the following error:
> > Error LGHT0204: ICE43: Component thing1 has non-advertised shortcuts.
> > It should use a registry key under HKCU as its Error LGHT0204: ICE57:
> > Component 'thing1 ' has both per-user and per-machine data with a
>
Scott Palmer wrote:
> Then I get the following error:
> Error LGHT0204: ICE43: Component thing1 has non-advertised shortcuts.
> It should use a registry key under HKCU as its Error LGHT0204: ICE57:
> Component 'thing1 ' has both per-user and per-machine data with a
> per-machine KeyPath.
>
> To
Scott Palmer wrote:
> I'm using WiX3.
> I am trying to make a shortcut as part of installing a
> component. The shortcut is to a launcher application that is
> installed in another component with a command-line argument
> that has the path to a file in the component that contains
> the shortcu
I'm using WiX3.
I am trying to make a shortcut as part of installing a component. The
shortcut is to a launcher application that is installed in another component
with a command-line argument that has the path to a file in the component
that contains the shortcut.
If I just use:
...
13 matches
Mail list logo
