ex-pat UK developer looking for nostalgia here 8)
They are probably looking for things like:
"License Agreement" should be "Licence Agreement" ("License" is a noun
"Licence" is a verb in UK English)
"Tickbox" instead of "Checkbox"
suffixes"-ise" instead of "-ize"
"Colour" instead of "Color".
Here's a clue:
MSI (c) (CC:18) [10:47:26:095]: Disallowing installation of component:
{CA4F7916-B9A9-5D6E-BD7A-98EFFC15AAA3} since the same component with
higher versioned keyfile exists
...
...
MSI (s) (EC:18) [10:48:26:172]: Executing op:
ComponentRegister(ComponentId={CA4F7916-B9A9-5D6E-BD7A
Sounds like you have sequenced RemoveExistingProducts towards the end of the
execute sequence.
Correct?
What happens if you sequence it early in the sequence so uninstall happens
first? (that _should_ solve the problem)
Is this new component in a feature whose state is not being migrated
correctl
>> To check for versions of 64-bit Windows use the VersionNT64 property.
This isn't strictly necessary. On 64 platforms, VersionNT64 _and_ VersionNT
properties are created.
It's ok to just check the VersionNT value.
You only really need to use the VersionNT64 property to determine if the OS
is 64
You have digitally signed binaries and cab files?
Perhaps the caching mechanism is trying to perform SCVP/OCSP?
Each signed file results a network timeout, which has a long default.
SCVP/OCSP is retried before failure is accepted as the result?
--
View this message in context:
http://windows-inst
Have you run process explorer to monitor what is going on while they are
being cached?
Perhaps something else is accessing the files (i.e. AV software?)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Caching-payload-sudden-terrible-performance-tp65
I don't think there's much the DIFXApp team can do to make the lib
foolproof/robust.
I'm pretty sure that DIFXApp is simply a wrapper around the win32 setupapi
API.
I've used both for the last few years.
In many cases, I've found that even when using the win32 api directly, it's
not possible to r
Hi,
Is it possible to create a single delta msp file that patches multiple
previous versions?
I'm struggling to find documentation on whether this is possible or not, so
I tried an experiment...
I'm using this cmd to create whole file patches successfully:
pyro -nologo .\v1.3.0\patch.wixmsp
8 matches
Mail list logo