All,
I am trying to put a Launch Condition within a a Feature, I cannot seem to
find any examples to do this. I am not even sure if i can.
My reason for this is that i have a feature, that only works with Windows
2003. And when or if the user chooses this feature and if the Operating
System is
sorry, I was concerned with the WIX dll/s that might be included within my
MSI/s.
I have used the WIX custom actions for IIS configurations. But its not clear
to me is what are the repercussions from the licensing aspect of things.
--
View this message in context:
http://n2.nabble.com/Licensing
hi all,
I have developed our Installer using WIX. We are now ready to sell our
product.
What i am concerned is about Licensing issues that might relate to WIX as
there are some dll/s that might be contained within our MSI/s.
Anyone out there who has had similar issues that know what i might ha
hi
I am using Wix 3.0.5419.0 with Visual Studio 2008 and Votive.
I use Build, rebuild and clean often, and have come to notice that when i do
regular "build" often, the msi does not seem to get changed correctly as the
time stamp does not change.
But when i do delete the contents of the releas
hi all,
well, it still does not work as the Launch condition still executed on
Uninstall.
I have tried "NOT Installed" and "OR Installed" within the condition and it
does not work.
i am using Wix 3.0.5419.0 and Votive with VS 2008.
Can someone maybe give me a sample code that work?
Thanks.
ir-2 wrote:
>
> Always add " OR Installed" to all of your LaunchConditions. If the product
> is already installed, you want to allow repairs and removals, including
> upgrades.
>
> -Original Message-
> From: spsingam [mailto:siva.poobalasin...@gmail.com]
&
e application isn't installed yet
>
> Best regards,
> Sebastian Brand
>
> Deployment consultant
> E-Mail: sebast...@instyler.com
>
> Instyler Setup - Creating WiX-based MSI installations, elegantly.
> http://www.instyler.com
>
> On 18.11.2009, at 05:13, spsi
hi,
how do i make sure that the Launch Condition only executes only on Installed
???
for now, my installer executes the Launch Condition on uninstall.
Anyone here with suggestions ?
--
View this message in context:
http://n2.nabble.com/Launch-Condition-on-Unistall-or-Remove-tp4023317p402331
hi All,
Problem:
I have installed some files, registry keys, directories and shortcuts from
my CoffeeShop.msi, this was developed using Wise for Windows Installer.
Then i found WIX, and developed and new product and a new MSI. The new msi
is called CoffeeCo.msi.
Now, when i execute my CoffeeC
hi all,
I have a Feature and i want to place a condition within this feature.
Example :-
the Feature is called SDK MAMAK Documentation. If the user selects this
feature a condition is invoked that will check to see if MAMAK is installed.
Only if MAMAK is installed will it allow the user to in
hi all,
i have failed to comprehend what KeyPath is all about.
Why would u want to put keypath within the or tags.
How would the keypath benefit these two elements.
--
View this message in context:
http://n2.nabble.com/WIX-3-0-KeyPath-tp3615801p3615801.html
Sent from the wix-users mailing
hi all,
i have failed to comprehend what KeyPath is all about.
Why would u want to put keypath within the or tags.
How would the keypath benefit these two elements.
--
View this message in context:
http://n2.nabble.com/WIX-3-0-KeyPath-tp3615828p3615828.html
Sent from the wix-users mailing
it would be nice to be able to use the "msiexec /a" and get the
Administrative install to work.
how would large organisations deploy msi/s if they cannot push it out via
group policy.
Bob Arnson-6 wrote:
>
> Chris Vigelius wrote:
>> Is there any chance to get the behaviour of uisample.msi wit
hi all,
I am using WixUI Mondo as my UI during the installation.
Now i have realised that i need to gather some user information, so i want
to introduce a dialog. I might choose to use this information later.
How do i do this ?
Regards.
:)
--
View this message in context:
http://n2.nabble.
14 matches
Mail list logo