On Thursday, September 27, 2007, at 01:59PM, "John Vottero" <[EMAIL PROTECTED]>
wrote:
>> On Thursday, September 27, 2007, at 01:00PM, "John Vottero"
>> <[EMAIL PROTECTED]> wrote:
>> >> Should something be properly escaping/quoting the argument? I can
>> slip
>> >> a couple of "s into my argumen
> On Thursday, September 27, 2007, at 01:00PM, "John Vottero"
> <[EMAIL PROTECTED]> wrote:
> >> Should something be properly escaping/quoting the argument? I can
> slip
> >> a couple of "s into my arguments string, but that feels like a
> >> layering hack.
> >
> >WiX and MSI have no way of knowing
On Thursday, September 27, 2007, at 01:00PM, "John Vottero" <[EMAIL PROTECTED]>
wrote:
>> Should something be properly escaping/quoting the argument? I can slip
>> a couple of "s into my arguments string, but that feels like a
>> layering hack.
>
>WiX and MSI have no way of knowing that your arg
> I'm generating a number of shortcuts to programs/scripts/etc that take
> arguments. One tester has noticed that a shortcut set up like:
>
>
> Name="logconf" LongName="Log Configuration Tool"
>
> Target="[INSTALLDIR]bin\wish.exe"
>
> Arguments="[INSTALLDIR]bin\logconfig"
>
> WorkingD
Hi,
I'm generating a number of shortcuts to programs/scripts/etc that take
arguments. One tester has noticed that a shortcut set up like:
fails because at install-time [INSTALLDIR] becomes C:\Program Files\Foo, and so
the expected single argument gets split into "C:\Program" and
"Files\Foo\b
5 matches
Mail list logo