Hi,

I am trying to deploy Silverlight 3 over the top of any previous versions. We need to do this as an MSI and not use the silverlight.exe (which upgrades fine). I have extracted the MSI and MSP and patched the MSI and use a transform which changes the product code. However, the install ignores the change of productcode and won't install as a previous version already exists. When I change the product code in the vendor MSI directly, it upgrades fine.

Has anybody had any luck upgrading Silverlight using the pached MSI with transform changes and not edited the MSI directly?

Regards,

Ben
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
- I can't say for certain, since I haven't pulled it apart, but I'll bet that the patch isn't a patch in the sense that we currently accept. MS has changed the way patches are used and now applies changes to packages using them rather than transforms. Witness the Office 2007 deployment instructions.
- Why on earth would you change the ProductCode?!?
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab
- Why on earth would you change the ProductCode?!?


Sorry, am I missing something. Why would I not change ProductCode in a Major Upgrade for the app to upgrade? I'm not being funny, I appreciate your assistance but don't understand why I wouldn't do this.
Answered 08/20/2009 by: bgold
Senior Yellow Belt

Please log in to comment
0
i think what vbscab is saying is that looking at your post it seems you are creating a patch for your msi and not an upgrade
if you are creating a patch then you don't need to change the product code
Answered 08/20/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
i don't know what tool you have Wise ?

have you tried using the UpgradeSync tool to compare the current package with the previous version of the package, and does the following to prepare the current package for a patch or upgrade:

Changes the PackageCode, ProductCode, and ProductVersion properties if necessary

then you can use the patch creation tool
Answered 08/20/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
Cygs,

The patch is supplied by MS, in pursuit of its bizarre switch to using patches as transforms.

BGold, additionally:

- it's not your MSI. You shouldn't mess with vendor-supplied MSIs, especially at such a fundamental level.
- I suspect Microsoft may well have worked out how to configure Upgrade tables by now :)
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
Sorry if I didn't make it clear but I'm using MS's Silverlight.MSP to create a patched administrative installation and then running this with my transform which makes our company standard changes and was then trying to change the productcode in my transform.

I know it's not idea to mess with the vendor MSi at this level, but how would you achieve what I need to do?

Cheers,

Ben
Answered 08/20/2009 by: bgold
Senior Yellow Belt

Please log in to comment
0
I repeat, why are you trying to change the product code?
Answered 08/20/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
And I repeat, I don't believe that the patch is a "real" patch but a transform replacement, a la Office 2007.

I shall now return to beating my head against this handy wall...
Answered 08/20/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: turbokitty

I repeat, why are you trying to change the product code?


I'm trying to change the ProductCode because I need it to upgrade. As it stands the UpgradeCode and ProductCode are the same for all versions, hence it not upgrading. When I change the ProductCode on the patched MSI directly - it upgrades, as it does also when installing using the wrapper Silverlight.exe. I want to do the same thing without editing the MSI, but it ignores the ProductCode transform change (the other transform changes take fine).

@VBSCAB - I have no experience of the new Office 2007 patches, I will look into it.
Answered 08/20/2009 by: bgold
Senior Yellow Belt

Please log in to comment
0
Let me rephrase why are you "trying to deploy Silverlight 3 over the top of any previous versions"?
What deployment tool are you using? You could use an msiexec command that patches existing installs and performs new installs if needed.
Answered 08/20/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
We are using our own bespoke installer tool which basically runs commands, effectively it can run any msiexec command in either base or user context.

What msiexec command are you thinking of? so far none have worked for me

Cheers,

Ben
Answered 08/21/2009 by: bgold
Senior Yellow Belt

Please log in to comment
0
Upgrade what, though? I haven't experienced any problem at my current client of letting the MSI install upgrade versions previous to v3. It sounds to me like you're trying to deploy v3 over existing installations of v3 which is truly bizarre.
Answered 08/21/2009 by: VBScab
Red Belt

Please log in to comment
0
This is definitely when upgrading from version 2.

How did you make the MSI and how are you installing it?

Thanks
Answered 08/21/2009 by: bgold
Senior Yellow Belt

Please log in to comment
0
OK, first, it seems the patch is an actual patch so apologfies for misleading anyone there. Nice to see consistent non-consistency from MS. I digress...

How did you make the MSI and how are you installing it? As you did: I patched the MSI and pushed it out via GP to a selection of test VMs. The difference is, I haven't touched the ProductCode.
Answered 08/21/2009 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab
As you did: I patched the MSI and pushed it out via GP to a selection of test VMs. The difference is, I haven't touched the ProductCode.


Strange, because it definitely doesn't work for me. I only tried changing the ProductCode after it didn't upgrade without changing it. I don't think I'm the only person to see this, as it is mentioned here -
[link]http://www.appdeploy.com/packages/detail.asp?id=1591[/link]
"You can then do a silent installation from the .msi, but first uninstall Silverlight 2.0 if it's installed otherwise it'll complain"

Seems the only difference is you are doing it via GP.
Answered 08/21/2009 by: bgold
Senior Yellow Belt

Please log in to comment
0
This does not help you...but it definitely worked for me...I have packaged 3-4 versions now....
Just to help you...follow that link you were you initally looking at....that should do the trick...
To recap...extract the exe...using /extract command...use winrar or simular to extract the patch from silverlight 7z.
Using any packaging tool, ANY MSI which you receive...never ever change the Productcode...or anything else...transform /patch the vendor MSI.....Are you sure that you are not confused by the upgradecode?
To troubleshoot....can the package be installed without an upgrade....have you tested this?
In the past, if I had problems with the Upgrade....I would do some logging with the switch /L*v c:\upgrade.txt
Also check the Upgrade table attributes and relate them with the ActionProperty details in the Property table. The upgrade is using the remove existing products action performs the upgrade and sequenced in the immediate actions, usually just after InstallValidate. Sometimes this can be moved before InstallFinalize....but thats another story...
Back to the problem...I am about to start version of Silverlight of 3.0.50106.0....what I noticed is one HKLM registry key in the silverlight.msi....which is just seems like a dummy or audit key with the version.
The rest is contained in the patch file: silverlight.msp....
Therefore, you should be able to apply the patch file using msiexec /p silverlight.msp /qn or /qb or whatever...
Hope this helps...
Answered 03/15/2010 by: tron2ole
Third Degree Blue Belt

Please log in to comment
0
Is it really wise to mess with the product code? I thought in the perfect world that was a major taboo...The eleventh commandment which stated 'Thou shalt not change the product (or package) code...But then, this is no perfect world we live in...
Answered 03/22/2010 by: Repackman
Purple Belt

Please log in to comment
0
Is it really wise to mess with the product code? I thought in the perfect world that was a major taboo...The eleventh commandment which stated 'Thou shalt not change the product (or package) code...But then, this is no perfect world we live in...

Even in the (very) unperfect world I live (and work) in, rule number one is

hands off the vendor MSI!!

so yea

P.S. should mention, I've had vendor MSIs make me laugh my ass off, I've had em make me cry in depair, but the rule still stands...Just so they can't say "that's not our product you installed, so kiss your support goodbye"
Answered 03/22/2010 by: pjgeutjens
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity