a side effect, to
> remove previous version(s). If you are using Windows Installer's progress
> bar, you may get one or two additional "passes" of the progress bar as the
> only widely noticeable side effect.
>
> -Original Message-
> From: Jonathan Hartley [mailt
6
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
>
>
> -Original Message-
> From: Jonathan Hartley [mailto:tart...@tartley.com]
> Sent: 05 October 2009 15:55
> To: General discussion for Windows In
his didn't change anything.
We have a second InstallExecuteSequence later in our main .wxs file. We
tried merging the two, in case the second definition replaced the first,
but to no avail.
Any help is much appreciated. Are we even going about this the right way?
Thanks,
Jonathan
--
J
the background after install, not synchronously during the
install itself.
Puzzled. Thanks for any ideas.
Jonathan Hartley wrote:
> Hi people,
>
> I'm asking for my .dll files to be ngened during install, at priority 0,
> which I understand should take place synchronously, while t
ity 1, 2 or 3 does change the
command visible in the logfile, by adding a "/queue:1" (or 2 or 3)
parameter, and the .dll files are then queued at the requested priority.
So the tag priority attribute does seem to be being recognised
and acted on, except when priority=0.
Many thanks f
;it does not remove the
> old version?" Because
> you then say that it overwrites the old version and there is only one item
> listed in ARP. That
> sounds like an update to me. Is the version in ARP the old version?
>
> Rob
>
> Jonathan Hartley wrote:
>
>
Incidentally, my Component Guids are all hard coded and constant.
Jonathan Hartley wrote:
> Hi all.
>
> I'm trying to add major updates. (Actually I'm migrating our Wix config
> from 2 to 3, and I can't see what I did to break major updates in the
> process.)
&g
Cop.
My wxs follows, with irrelevant bits removed:
--
Jonathan Hartley Made of meat. http://tartley.com
tart...@tartl
ntries
> from both the SchedNetFx and ExecNetFx actions to see if there are any
> clues...
>
> -Original Message-
> From: Jonathan Hartley [mailto:tart...@tartley.com]
> Sent: Thursday, September 24, 2009 7:31 AM
> To: General discussion for Windows Installer XML tools
else do I need
to do?
Any further clues as to what's going on would be much appreciated.
Many thanks
Jonathan
Jonathan Hartley wrote:
> Thanks Blair,
>
> We might need to support early versions of Windows. - we're writing a
> downloadable desktop application for wides
ll go read about this.
Jonathan
Blair wrote:
> Do you really need to support Windows Me or earlier?
>
> In your Package element, set the InstallerVersion attribute to 200 or
> higher.
>
> -Original Message-----
> From: Jonathan Hartley [mailto:tart...@tartley.com]
e able to ngen
them synchronously, as part of the install, as we did with Wix2. I can't
understand the above warning, and haven't been able to Google anything
useful either.
Does anyone have any clues, or suggestions of what I should be reading
up on?
Many thanks,
Jonathan
--
12 matches
Mail list logo
