Hi all,
I finally took the plunge, downloaded WiX 3.5 (the Dec 30th edition),
installed it, and even read some of the documentation.
What I would like to achieve: Create a setup for one of the projects
in our main solution file and have the .msi built as part of our TFS
build.
One of the topics
Personally I'm not a fan of defining an installer by scanning at build time.
It's not deterministic enough for me. I'm also not really a fan of using
project references. If you are interested, take a look at IsWiX over at
http://iswix.codeplex.com. Take a look at the source code and see how
I have a similar scenario and my workaround is to allow same version
upgrades. This means 3.0.1.14900 will upgrade 3.0.1.14500 (but it also
means 3.0.1.14500 will upgrade 3.0.1.14900 which might be undesirable).
In WiX 3.5 you can do this by setting
MajorUpgrade/@AllowSameVersionUpgrades - otherwi
The concept of harvesting across project references is still a bit nascent
in WiX. We tried a couple experiments in WiX v3.5 but started slipping into
a rabbit hole of issues. Things that you would expect to just work don't.
So, the harvesting feature was turned off in WiX v3.5 and you have to
expl
Terrifying. You must be in some really controlled environments for that to
work out well.
The Windows Installer (for whatever reason) chose to ignore the 4th version.
It boggles my mind that "management" gets to decide a versioning scheme that
won't work. You might as well pick a different instal
Rob-
The comment to not use MSI aside, it is pretty hard for me to justify to
build engineers, software developers and product managers that yes they can
build DLL's as 1.0.0.0 and 1.0.0.1 but that they can't build their MSI as
1.0.0.0 and 1.0.0.1 because MSI will see it as 1.0.0 and 1.0.0.
It is very controlled, major minor are the application version, build
changes daily and revision on each build - that is a very common
scenario and I don't at all see that as "terrifying". I have looked at
various version schemes and this is only one that works reliably from
build to build, is idem
Oh, I can't justify the Windows Installer choice either. I also can't change
it.
Software engineering is fun because we can build our own Lego blocks to
build what we want to build. Remember 30 years ago how hard it was to build
smooth looking things with Legos? The parts just did not exist (they
>> PS: If you don't thinking versioning is that important to your
product then you probably think I'm over exaggerating the issue.
100% agree, version is 'the' most important thing I do. I know you
replied to Chris but I thought I'd add my comments...
This is why I have had to choose the approach
Hi:
I'm currently developing a custom Table and have a few questions regarding the
element:
What is the difference between:
Path,
Paths ,
and
AnyPath
Do any of these types include the filename?
Also if I specify property in the category field, will this set a property to
the value specified in t
I have created a msi file and it seems to work fine but the compression does
not seem to work. If my included files are 3mb I end up with a 4.5mb msi.
If I zip the files I end up with 1mb.
I have the following line in my wxs file
Mszip should be default anyway.
What should I do so the
MSZIP is not DEFLATE (the compression algorithm used by .zip files). You
might play with the other options to see what works best.
Compression is very dependent on the input.
On Sun, Jan 16, 2011 at 6:30 PM, Ralph Esslinger <
reesslin...@matthews.com.au> wrote:
> I have created a msi file and it
All of the column data types are defined here:
http://msdn.microsoft.com/en-us/library/aa367869(v=VS.85).aspx
They only affect validation. When you read the column, it's still going to
only be a string, integer or binary data.
On Sun, Jan 16, 2011 at 5:50 PM, Sean Farrow
wrote:
> Hi:
> I'm curren
I saw you're reply later and was going to get to it later (er, now).
Personally, I would chose to have an error that says, "An equal version of
this product is installed. Remove it first, before installing." Maybe with a
bit better error message.
The lack of 4th version in the installer does make
Hi:
I have the following custom table definition:
12
0
522
"HKLM\Software\Freedom
Scientific\JAWS\12.0\Target
As can be seen, a first row is partially filled in.
My queries are:
Firstly, c
15 matches
Mail list logo
