I have an msi package which comes out to 77MB when compression is set
to "high". Inspecting the msi file shows that the space is almost
entirely consumed by the contained cab file. If I take the same files
in that cab file and compress them with 7zip it comes out to 27MB.
Normally I wouldn't care t
Please bear with me if I am missing anything obvious since I recently started
experimenting WIX 3.0 for building patches.
I understand that we can generate patches using either PCP file or WIX
directly. I decided to go with the latter approach but I am running into some
issues with it. The main
This is not a one off as it will need to be changed if the interface
changes.
When I described the process to be team they all said there is no way
they are doing that, and that I should just use /regserver and
/unregserver custom actions,
1. They could not understand why a supported feature s
OK, I finally figured this out (I am open to other suggestions). After
installing with Windows7 Platform SDK on my desktop (64bit Windows7), and our
build servers I discovered that for whatever reason the 32bit platform SDK does
not include the bootstrappers like the 64bit version does.
Howeve
I have a question on Verbs.
"Error CNDL0019 : The Verb/@TargetProperty attribute cannot be specified
because the element is advertised."
The WiX manual does not say *why* I cannot use Verb/@TargetProperty with
advertised ProgIDs.
(1) Why can't I use this combination?
(2) What progra
The WiX manual contains the following:
"The first is a RemoveFolder element, which ensures the
ApplicationProgramsFolder is correctly removed from the Start Menu when the
user uninstalls the application. The second creates a registry entry on
install that indicates the application is installed.
In article
,
Tom Crozier writes:
> The lengthy CA validates the users credentials [...]
Why does your application need a user's credentials?
If your application needs to do something that requires a specific
privelege, create an account that has interactive logins disabled that
has the n
Tom Crozier wrote:
> When I try using 'asyncNoWait' I get:
> error CNDL0038 : The CustomAction/@Return attribute's value, 'asyncNoWait',
> cannot be specified without attribute ExeCommand present.
>
Right, sorry; it's valid only for .exe CAs.
> What I don't understand is that I would think the
I believe it is, but I also thought that SpawnWaitDialog should also allow the
dialog to be displayed and processing to continue until the property condition
is met. In previous test versions I had called SpawnWaitDialog first thinking
that it would be run in a separate process or thread and all
The lengthy CA validates the users credentials via a web service which can take
upwards of a minute on some systems. I validate the credentials during the UI
phase so that there are no errors during the install phase, (Background the
entire install takes over a half an hour to perform because it
10 matches
Mail list logo
