tag:blogger.com,1999:blog-985159635193633235.post953803688368534340..comments2023-06-14T01:53:47.089-07:00Comments on ISWIX: Versioning MSI Packages: WiX vs InstallShieldChristopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-985159635193633235.post-59066536317341157672007-09-26T23:29:00.000-07:002007-09-26T23:29:00.000-07:00InstallShield listen to their customers?Are you su...InstallShield listen to their customers?<br>Are you sure?<br>What's your technique to get them to listen to you? Megaphone? Kidnap? Bomb threats? <br>I've tried them all and they have never listened to mefrednoreply@blogger.comtag:blogger.com,1999:blog-985159635193633235.post-71130279129124392172007-09-27T01:58:00.000-07:002007-09-27T01:58:00.000-07:00In WiX, since in the other blog's example the ...In WiX, since in the other blog's example the product version is already in a variable, why not just pass the variable in to light as a -d argument? I do something like this with msbuild:<br><br><CreateProperty Value="ProductVersion=$(AssemblyFileVersion);$(DefineConstants)"><br> <Output TaskParameter="Value" PropertyName="DefineConstants" /><br></CreateProperty><br><br>Johnjdh28http://www.blogger.com/profile/10806320759268315310noreply@blogger.comtag:blogger.com,1999:blog-985159635193633235.post-19565212091152842032007-09-27T11:08:00.000-07:002007-09-27T11:08:00.000-07:00Chris, you weren't very clear in stating that ...Chris, you weren't very clear in stating that is BRAND NEW functionality to InstallShield. Before you either had to the IS Automation object or edit the project XML during the build process.<br><br>...and it's that easy in WiX as well. We use a preprocessor variable and accomplish the exact same thing.<br><br>Why all the nitpicking on WiX? It's not like InstallShield has had over 15 years to mature their product or anything.Aaron Shurtshttp://www.blogger.com/profile/16538587727045104430noreply@blogger.comtag:blogger.com,1999:blog-985159635193633235.post-66558611788876331422007-09-27T11:21:00.000-07:002007-09-27T11:21:00.000-07:00Actually I said "...but starting with Instal...Actually I said "...but starting with InstallShield 2008...". I'm sorry if this wasn't clear enough.<br><br>Actually I'd say that InstallShield is probably around 8 years old and that it works against it, not for it. It's probably alot easier to work on WiX in .NET. The only problem I see with WiX is project managment ( not meant to infer project manager ) / requirements / resource allocation.Christopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comtag:blogger.com,1999:blog-985159635193633235.post-73283666817419219202007-09-27T13:44:00.000-07:002007-09-27T13:44:00.000-07:00I believe they were founded in 1987. I was referr...I believe they were founded in 1987. I was referring to their product line as a whole, not specifically the Windows Installer product.<br><br>WiX is not without its flaw, but it's unfair to compare it to InstallShield that has many, many times more man hours and resources allocated to it than WiX.Aaron Shurtshttp://www.blogger.com/profile/16538587727045104430noreply@blogger.comtag:blogger.com,1999:blog-985159635193633235.post-17488790860643492342007-09-27T14:42:00.000-07:002007-09-27T14:42:00.000-07:00Thanks for the comment on my blog.I agree, there m...Thanks for the comment on my blog.<br><br>I agree, there must be an easier way to do it, but many shops (esspecially those with blanket MSDN licences) feel compelled to go all the way with Microsoft.<br><br>So.. without purchasing Installshield, is there still an easier way to do this? :)Andrewnoreply@blogger.comtag:blogger.com,1999:blog-985159635193633235.post-87113113290878261812007-10-03T14:22:00.000-07:002007-10-03T14:22:00.000-07:00Getting the install team at MVSN to listen is easy...Getting the install team at MVSN to listen is easy: be thorough, professional, consistent and offer examples. Chris does a great job of all four, and he knows his craft inside-out.bobnoreply@blogger.comtag:blogger.com,1999:blog-985159635193633235.post-60774600373461410272007-10-03T20:45:00.000-07:002007-10-03T20:45:00.000-07:00I'm in a very pro-Microsoft shop. We use a lo...I'm in a very pro-Microsoft shop. We use a lot of Microsoft technologies in our solution. Everyone has a seat for VS TFS and an MSDN subscription. But, that doesn't mean you can't incorporate technology from other vendors. We use Sybase PowerBuilder, Oracle, DB2, Infragistics and of course InstallShield. <br><br>The truth is while we do use Windows Installer for the runtime, Microsoft MSI authoring tools are inferior. Orca isn't designed to be used as an authoring tool. VDPROJ truely is limited and while WiX has some really great features, it really a bear to work with. WiXAware fills in these gaps but it's not really ready for prime time either.<br><br>On the other hand, InstallShield integrates very nicely with Visual Studio so I have no problems with using it.Christopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.com