Hi,
HowTo check for pressed Cancel Button in Custom Action ?
Wichtiger Hinweis: Diese E-Mail und etwa angeh?ngte Dateien k?nnen vertrauliche
Informationen enthalten und sind ausschlie?lich f?r den/die Adressaten
bestimmt. Sollten Sie irrt?mlich diese E-Mail erhalten haben, bitten wir Sie,
uns
iResult = MsiProcessMessage(hInstall, INSTALLMESSAGE_PROGRESS,
hProgressRec);
if ((iResult == IDCANCEL))
return ERROR_INSTALL_USEREXIT;
http://msdn.microsoft.com/en-us/library/aa367525(v=vs.85).aspx
--
View this message in context:
http://windows-instal
The always overwrite flag in InstallShield just sets the FileVersion column to
65535.0.0.0. WiX has the DefaultVersion field, which should duplicate the
experience. Alternatively, just modify the MSI post-build for this one-off. It
would be easier if you were not using an assembly file because y
This shouldn't apply to later MSI engines - according this KB article
it shouldn't be a problem if you make sure you have at least MSI 4.0,
or ship the 4.5 redist.
http://support.microsoft.com/kb/905238/en-us
but I vaguely remember the original MSI needs installing with a
correct MSI engine too,
Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar
basti...@careercontrol.nl.
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Jav
I have two different products/bundles that install different versions of
the same msi package. I had expected that the bundle would detect the
existing installation of the msi and log it as an upgrade, but instead
it's logging it as "absent" and the subsequent execution of the package
runs the
The issue was fixed in MSI 5.0 or if you install the hotfix
(http://support.microsoft.com/kb/972397/EN-US), but that won't help him because
he's down-revving a versioned file. Even if it remains after the major upgrade,
it will still be version (n) and not (n - 1).
To be honest, I think sequenc
I may be talking out the side of my mouth here,, but why cant he
remove version N doing a version check like so:
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/check_the_version_number.html
and then if the Installed file >= N remove said file and replace with N - 1
Car
As far as I'm aware, neither FileSearch, DirectorySearch, RemoveFile or
RemoveFileEx can target Assemblies because the paths to them are generated and
the FileKeys don't point to those assembly paths.
Otherwise it would be easy to just do a Remove File table entry and all will
work "automagica
Dobt all Assemblies get added to the GAC though?? Then use the Version
Search to Search the GAC. Could be totally wrong, I just know how it
feels when a relatively easy task turns into a mountain...
Quoting Bryan Wolf :
> As far as I'm aware, neither FileSearch, DirectorySearch, RemoveFile
They could also be in the WinSxS directory but yes.
I just generally would consider traversing the GAC as if it were a directory
structure worse than just setting the FileVersion or rescheduling REP before
CostFinalize because you can't guarantee that Microsoft doesn't decide to
reorganize the
Good Call, ill crawl back to my corner now lol :)
Quoting Bryan Wolf :
> They could also be in the WinSxS directory but yes.
>
> I just generally would consider traversing the GAC as if it were a
> directory structure worse than just setting the FileVersion or
> rescheduling REP before CostFi
Folks,
Thanks for all the responses.
This issue happens even with normal files(not just assemblies)
MSI (s) (48:F0) [07:39:21:024]: Disallowing installation of component:
{4D2EB851-13AC-500F-9704-AB78102F8D0F} since the same component with higher
versioned keyfile exists
I dont want to implemen
Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar
basti...@careercontrol.nl.
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Jav
14 matches
Mail list logo
