It is kind of complicated in my case. The IT admin would be installing a package on the machine. During installation, it is going to talk to the server and take up one slot in the account(receives a cert). The next time either the IT admin or the local admin runs the package on this machine, it will see that it has already received a cert from the server and hence make this execution a NOOP. So, even if the system locale is changed and the package is run again, I want the package to verify that certificate is present and, if yes, make the execution a NOOP. I won't be able to have this functionality if I have a different ProductCode for each language, because it will then be considered a major upgrade, right?
Looking at the previous year's thread on this - http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/When-to-change-Product-Id-ProductCode-two-editions-of-the-same-product-td3832979.html#a3832979. I don't have a patching story for my installation package. The admin will just install it once. There is no repair story or upgrade story to it. The package would either enroll the client into the service or it fails. If it succeeds, then future runs of the same package(of any language) should be NOOP. If it fails, admin will fix the problem on the client machine and run the package again or get a new package from us and run it. As I said, my main scenario is that the package should never do a major upgrade, because it eats up an account slot, unnecessarily, for which the admin paid money. So, I'm trying to see if I'm missing anymore scenarios where I would get into trouble if I use the same productCode for all the languages. -Pratap. On Wed, Jun 16, 2010 at 6:56 PM, Sascha Beaumont <sascha.beaum...@gmail.com>wrote: > Check the archives for more information, I asked a similar question > sometime last year. I can't find the exact thread, but ended up being > convinced to make the change. I did however find a list of pointers > from Rob around localization - changing the PackageCode was important > enough to be item 0 ;) > > > > 0. *Every* MSI should have a different PackageCode. Even two builds of > > the same MSI. > > > Sascha > > > > On Thu, Jun 17, 2010 at 2:28 AM, Pratapa Reddy Sanaga > <pratap.san...@gmail.com> wrote: > > Hi, > > > > I was going through an example for localization and came across this MSDN > > page http://msdn.microsoft.com/en-us/library/aa372369. It says that we > must > > change the productCode for every localized package. Is this a necessary > > condition or just a good practice? I'm planning to create MSIs for > different > > languages, create transforms with english as base package, embed these > > transforms into the base package and have a bootstrapper that would apply > > the right transform and install the package. So, for this scenario, do I > > need to create different ProductCodes for different language MSIs? > > > > If I have the same product code for all the language MSIs and tomorrow if > I > > find a localization bug in one language, will there be any implications > in > > this servicing process because of the same productCode used in the first > > place? > > > > Thanks, > > Pratap. > > > > -- > > Vote for loksatta = vote for a better future > > > ------------------------------------------------------------------------------ > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > lucky parental unit. See the prize list and enter to win: > > http://p.sf.net/sfu/thinkgeek-promo > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Vote for loksatta = vote for a better future ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
