1. You should use different ProductCodes. Otherwise it will be very
difficult to tell what product a user has installed. The real kicker (which
you may not be hit by directly) is if you ever try to create patches. Using
the same ProductCode will make patching basically impossible.
There is really no good reason to use the same ProductCode (except it might
be easier up front).
2. I would use separate ProductCodes for each "product type". If you look at
Office they have a similar sort of system ("Standard" vs. "Professional" or
whatever the names are today). Each of those products have a different
ProductCode. Upgrading from one to the other would be interesting. If you
have only major upgrades then its pretty straight forward, you'll be doing a
major upgrade. <smile/>
virtually, Rob Mensching - http://robmensching.com
On Thu, Oct 15, 2009 at 5:50 PM, Sascha Beaumont
<sascha.beaum...@gmail.com>wrote:
> Hi All,
>
> This isn't so much a WiX specific question, but more of a Windows
> Installer one... however those on the list seem to have a pretty good
> understanding of all the "rules" we should be following so I'm hoping
> someone can point me in the right direction.
>
> Currently for our main product I'm using two Product/@Id with each
> release - one for x86 and one for x64. However I'm using the *same*
> Product/@Id and Upgrade/@Id for the 6 different languages we ship.
>
> Question 1 - Looking at "ProductCode Property" [
> http://msdn.microsoft.com/en-us/library/aa370854(VS.85).aspx<http://msdn.microsoft.com/en-us/library/aa370854%28VS.85%29.aspx>]
> I see a
> requirement that the ProductCode must differ for different versions,
> and languages. I'm just wondering why a different code for a different
> language if I don't permit them to be installed side-by-side? The
> packages are identical, we are just using Lingobit Localizer to
> replace the resources in a pre-WiX build step and using a different
> .wxl for the WiX build.
>
> Question 2 - Looking at "Changing the Product Code" [
> http://msdn.microsoft.com/en-us/library/aa367850(VS.85).aspx<http://msdn.microsoft.com/en-us/library/aa367850%28VS.85%29.aspx>]
> I see
> that adding new features is permitted without changing the product
> code. However as the feature is only requested by a small portion of
> our customer base... we're wanting to ship two versions of the same
> MSI, one with the additional feature (which almost doubles the
> download size) and one without. Should I be changing the product code
> here or not?
>
> Effectively in Question 2 my aim is to distribute two editions of the
> same product, prevent them being installed simultaneously, and permit
> the user to upgrade from the "Standard" to the "Enterprise" release.
> We always release major upgrades and so separating things into two
> distinct product lines is a feasible one - I'm just trying to figure
> out if I do so (different product codes, upgrade codes, etc) can I
> prevent the user from installing one over the other just by using the
> upgrade table? Or will I need some complicated CA's?
>
> Sascha
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
