I would vote for make vital true by default with the option of setting
it off via the command line. I have never really thought there are many
occasions when making a file optional would be ok. I would guess that a
lot of installs (mine included) don't set this but that clicking
ignore would
There is a recent PSDK.MSI thread where Simon Scott suspects a FilesInUse
pattern bug:
http://groups.google.com/group/microsoft.public.platformsdk.msi/browse_thread/thread/17f76202ee2b2742/dc061211ad4db61a?lnk=raot
He thinks MSI is having a false positive on a locked file and that
Реклама в новом виде. Рассылки по электронной почте на специальных условиях
только для вас (бесплатный тест).
510-72-66
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting
I would suggest this presumes that the person doing the install knows
what they are doing! In a corporate environment that may be true and in
that case you could build installs with vital off (having said that most
of our installs are run silently so failing is a better option). I think
the
As I said, that failing install is going to generate a report call either way.
In this scenario, the install may actually succeed and thereby avoid that
support call. Also if that file is critical an installed product could
possibly still launch the program which in turn could perform it's
Hi all,
I'm authoring an installer that contains several merge modules (among
the other things):
- Microsoft_VC80_CRT_x86.msm
- policy_8_0_Microsoft_VC80_CRT_x86.msm
- Microsoft_VC80_DebugCRT_x86.msm
- policy_8_0_Microsoft_VC80_DebugCRT_x86.msm
The installer has been building and installing
6 matches
Mail list logo
