Thanks a lot :)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-a-input-property-tp7586501p7586597.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Can someone point me in the direction to reach this goal:
My requirement is for three flavors of the application: Lite, Basic, and
Premium; each released as a separate MSI package.
The user can only move up the chain. For example, if the Basic is
installed, Lite cannot be installed. If, in the
It's pretty easy to distribute SQL ce DLLS, you can just deploy the files. Here
is a blog that describes this.
http://erikej.blogspot.com/2011/02/using-sql-server-compact-40-with.html
I made my own merge module
Hope this helps
Dan
Sent from my iPhone
On Jun 16, 2013, at 6:46 AM, Michael Stol
Hi,
I'm experiencing unwanted reboot when upgrading our product from one version to
another. This is seems an expected behavior, but I was not expecting it :) The
question - is there any way to prevent ANY reboot? Or maybe I can determine it
prior upgrade and prevent upgrade? Latter will work
I'm authoring a burn package for SQL CE 4.0.
Are there any preexistend SQL CE packages?
The package should use msi files that are downloaded automatically. But
the only msi files for download, that i could find where the SP1 CTP
version.
Is there a msi package out there with a permanent downloa
5 matches
Mail list logo