Great, I've been looking for version comparision for a long time.
I've updated the conditions (see below). This seems to work, but I
didn't do a lot of testing, yet.
http://go.microsoft.com/fwlink/?LinkID=253117";
DetectCondition='NOT VersionNT64 AND
ndows Installer XML toolset.'
Subject: Re: [WiX-users] SQL CE 4.0 Package
I Just talked to Wix and they were supposed to unsubscribe me to all these
emails!!!
-Original Message-
From: Nicholas Pierce [mailto:nicholas.pie...@permasense.com]
Sent: Thursday, June 27, 2013 10:50 AM
T
] SQL CE 4.0 Package
Just write the version number, with a v in front and no quoting (i.e.
SQL_SERVER_VERSION >= v10.50).
Nicholas
On 27 June 2013 16:06, snowkoan wrote:
> Cool. So we have a Burn variable called SqlCe40Version, that contains
> a version string like "14.0.0.0"
Just write the version number, with a v in front and no quoting
(i.e. SQL_SERVER_VERSION >= v10.50).
Nicholas
On 27 June 2013 16:06, snowkoan wrote:
> Cool. So we have a Burn variable called SqlCe40Version, that contains a
> version string like "14.0.0.0"
>
> How can we do a version comparison
Cool. So we have a Burn variable called SqlCe40Version, that contains a
version string like "14.0.0.0"
How can we do a version comparison with a hardcoded string, like
"v4.0.8876.1"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SQL-CE-4-0-Packag
To get *version* comparisons the quotes from around the version numbers
(that makes them strings) and put a "v" in front. So the following should
evaluate to true: "v4.0.0.0 < v14.0.0.0"
On Fri, Jun 21, 2013 at 12:21 AM, Michael Stoll wrote:
> Here're the SQL CE 3.5 and 4.0 packages.
>
> Th
Here're the SQL CE 3.5 and 4.0 packages.
There's a significiant difference in the behavior of those two!
The SQL CE 4.0 packages detect SQL CE 4.0 of ANY language. While 3.5
detects only a specific language.
The SQL CE 4.0 package could be altered to look for a specific language,
but I like the
I've got a SQL CE 3.5 package, that's working well. It uses MSI files,
so detect is easy.
Note: There's an issue with the x86 on x64 machines:
(http://support.microsoft.com/kb/974247)
The links are for german culture installers.
Am 17.06.2013 16:03, schrieb Rob Mensching:
If you get it work
If you get it working well, it'd be great if you could help us expand the
provided packages and we can get that code in to maybe the SqlExtension.
On Mon, Jun 17, 2013 at 6:47 AM, Michael Stoll wrote:
> I might have been unclear, sorry.
>
> I don't want to create the msi package, I just want to
I might have been unclear, sorry.
I don't want to create the msi package, I just want to bootstrap it.
If there's no msi installer, I'd stick to the exe installer.
The exe package should look somewhat like this (not testet yet)
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schema
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
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
12 matches
Mail list logo
