On 13/11/2012 15:49, Rob Mensching wrote:
> What about using a Feature/Condition instead?
Thanks, that works.
--
Bruce Cran
--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-de
I never tried.
On Wed, Nov 21, 2012 at 8:16 AM, Bruce Cran wrote:
> Should WixStdBA work on Server Core? It mostly seems to, but Options ->
> Browse isn't functional since Core doesn't have the common dialogs -
> apparently it can be made to work by adding some flags
> (
> http://social.technet
There is no reason to be honest. They can end up being in the same MSI in
different features.
I have 2 MSI's now, because after migrating from 3.5 to 6, I decided to use
Burn. This meant removing my Merge Modules (msm A & B) (since it's not
recommended anyway).
So I converted them into msi's whi
Using a custom action is something I hadn't considered. Here's a past posting
where someone was doing that:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/OpeFileDialog-C-Custom-Action-td5860149.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.68755
Should WixStdBA work on Server Core? It mostly seems to, but Options ->
Browse isn't functional since Core doesn't have the common dialogs -
apparently it can be made to work by adding some flags
(http://social.technet.microsoft.com/Forums/en-GB/winservercore/thread/f9f1f6f1-960a-4ddf-94d4-86b7c
When a reboot is pending, Burn fails with the message:
You must restart your computer to complete the rollback of the software.
I'm wondering why it mentions 'rollback' because in this case the reboot
is pending following a successful installation of a driver.
--
Bruce Cran
--
Just a few questions to help clarify:
What do you mean when you say it's not working?
Where are you putting the PermissionEx elements? Inside of a RegistryKey
element?
In your code sample you're using curly braces: {username}. Is that how you
have it for real?
--
View this message in context:
WiX is a layer on top of Windows Installer, which has a certain look that
can't be changed. You could customize the look by adding a bootstrapper
project and writing a custom BA using WPF or WinForms, but that would be
some extra work on your part for such a small requirement.
--
View this messa
I'm curious about your setup. What is it about it that make having two MSIs
worthwhile? Did you not want to have two Features in a single MSI?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Editing-files-from-the-Bootstrapper-Application-tp7582014
Hi there,
I'm having a Bootsrtapper application, where I have 2 msi's chained. A and B
Msi A represents a codebase, that enables functionality based on a
configuration file.
Msi B depends on A.
In the UI, I am planning to have a screen, where you can select what
functionality you want from the pr
10 matches
Mail list logo