Re: [WiX-users] RemoveExistingProducts after the InstallFinalize action still needed so that Major Upgrades don't remove assembly from GAC ?

2012-01-09 Thread CristianG
Thanks for mentioning those hotfixes.  

In the end I've included them in the bootstrapper. It seems to be the right
way compared to increasing the file version of the assemblies.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingProducts-after-the-InstallFinalize-action-still-needed-so-that-Major-Upgrades-don-t-re-tp7137858p7167252.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] RemoveExistingProducts after the InstallFinalize action still needed so that Major Upgrades don't remove assembly from GAC ?

2012-01-03 Thread CristianG
I've done some more tests and it seems that on Windows Installer 4.5 the
assembly is removed from GAC after a major upgrade. 
Good to see that at least on 5.0 got fixed.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingProducts-after-the-InstallFinalize-action-still-needed-so-that-Major-Upgrades-don-t-re-tp7137858p7146124.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] RemoveExistingProducts after the InstallFinalize action still needed so that Major Upgrades don't remove assembly from GAC ?

2012-01-03 Thread Wilson, Phil
There is a hotfix available, not sure if this has been mentioned in this 
thread. 

http://support.microsoft.com/kb/972397/EN-US 

More Info says you also need http://support.microsoft.com/kb/983280 

Phil W 

-Original Message-
From: CristianG [mailto:cristian.gherghine...@gmail.com] 
Sent: Tuesday, January 03, 2012 1:09 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] RemoveExistingProducts after the InstallFinalize 
action still needed so that Major Upgrades don't remove assembly from GAC ?

I've done some more tests and it seems that on Windows Installer 4.5 the
assembly is removed from GAC after a major upgrade. 
Good to see that at least on 5.0 got fixed.

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingProducts-after-the-InstallFinalize-action-still-needed-so-that-Major-Upgrades-don-t-re-tp7137858p7146124.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail 
recept...@invensys.com. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).



--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] RemoveExistingProducts after the InstallFinalize action still needed so that Major Upgrades don't remove assembly from GAC ?

2011-12-30 Thread CristianG
Hi,

There is  http://support.microsoft.com/kb/905238 a knowledge base article  
(mentioned also on the WiX Documentation) that describes the case of an
assembly from GAC missing after a major upgrade. One of the solutions was to
schedule *RemoveExistingProducts *action to occur after the *InstallFinalize
*action. 

However, after the following test the assembly was still in GAC.

The test:
Using WiX 3.6, created a new setup project, with version 1.0.0.0 and
*MajorUpgrade *element default, containing a dll to install into GAC. 
Install this small setup. Windows Installer 5.0
Create version 2.0.0.0, change Product Id (*ProductCode*) and leave the
*MajorUpgrade *element default. The assembly for GAC remained the same.
Checked with Orca and *RemoveExistingProducts *was scheduled after
*InstallValidate *
Do a major upgrade.
The assembly remained in GAC.
In the log file there is something like:



Does that line from the log mean that the knowledge base article doesn't
apply anymore ?

Did I miss something and the *RemoveExistingProducts * action still needs to
be scheduled after *InstallFinalize *action so that the assemblies from GAC
are not removed after a major upgrade ?


Thanks,
Cristian

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingProducts-after-the-InstallFinalize-action-still-needed-so-that-Major-Upgrades-don-t-re-tp7137858p7137858.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] RemoveExistingProducts after the InstallFinalize action still needed so that Major Upgrades don't remove assembly from GAC ?

2011-12-30 Thread Peter Shirtcliffe
My colleague investigated some scenarios like this a few months ago. He found
that when not changing the assembly version, then using the -fv switch on
light and increasing the file version enabled a major upgrade of an assembly
in the GAC with early RemoveExistingProducts to succeed. 

Without -fv, it failed on Win2003 with MSI 4.5 but succeeded on Win7 with MSI
5. 

When changing the assembly version too, the major upgrade succeeded.

It might be worth making a quick test installer for the scenarios you are
interested in to see if you get the same results. I'd look at the GAC, rather
than the log, as the indicator of what happened, to avoid misinterpreting it.

-Original Message-
From: CristianG [mailto:cristian.gherghine...@gmail.com] 
Sent: 30 December 2011 11:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RemoveExistingProducts after the InstallFinalize action
still needed so that Major Upgrades don't remove assembly from GAC ?

Hi,

There is  http://support.microsoft.com/kb/905238 a knowledge base article  
(mentioned also on the WiX Documentation) that describes the case of an
assembly from GAC missing after a major upgrade. One of the solutions was to
schedule *RemoveExistingProducts *action to occur after the *InstallFinalize
*action. 

However, after the following test the assembly was still in GAC.

The test:
Using WiX 3.6, created a new setup project, with version 1.0.0.0 and
*MajorUpgrade *element default, containing a dll to install into GAC. 
Install this small setup. Windows Installer 5.0
Create version 2.0.0.0, change Product Id (*ProductCode*) and leave the
*MajorUpgrade *element default. The assembly for GAC remained the same.
Checked with Orca and *RemoveExistingProducts *was scheduled after
*InstallValidate *
Do a major upgrade.
The assembly remained in GAC.
In the log file there is something like:



Does that line from the log mean that the knowledge base article doesn't
apply anymore ?

Did I miss something and the *RemoveExistingProducts * action still needs to
be scheduled after *InstallFinalize *action so that the assemblies from GAC
are not removed after a major upgrade ?


Thanks,
Cristian

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingP
roducts-after-the-InstallFinalize-action-still-needed-so-that-Major-Upgrades-
don-t-re-tp7137858p7137858.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] RemoveExistingProducts after the InstallFinalize action still needed so that Major Upgrades don't remove assembly from GAC ?

2011-12-30 Thread Wilson, Phil
I believe the issue is fixed in MSI 5.0. I've forgotten who told me but I think 
it was somebody in Microsoft. 
Phil W 

-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] 
Sent: Friday, December 30, 2011 4:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RemoveExistingProducts after the InstallFinalize 
action still needed so that Major Upgrades don't remove assembly from GAC ?

My colleague investigated some scenarios like this a few months ago. He found
that when not changing the assembly version, then using the -fv switch on
light and increasing the file version enabled a major upgrade of an assembly
in the GAC with early RemoveExistingProducts to succeed. 

Without -fv, it failed on Win2003 with MSI 4.5 but succeeded on Win7 with MSI
5. 

When changing the assembly version too, the major upgrade succeeded.

It might be worth making a quick test installer for the scenarios you are
interested in to see if you get the same results. I'd look at the GAC, rather
than the log, as the indicator of what happened, to avoid misinterpreting it.

-Original Message-
From: CristianG [mailto:cristian.gherghine...@gmail.com] 
Sent: 30 December 2011 11:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RemoveExistingProducts after the InstallFinalize action
still needed so that Major Upgrades don't remove assembly from GAC ?

Hi,

There is  http://support.microsoft.com/kb/905238 a knowledge base article  
(mentioned also on the WiX Documentation) that describes the case of an
assembly from GAC missing after a major upgrade. One of the solutions was to
schedule *RemoveExistingProducts *action to occur after the *InstallFinalize
*action. 

However, after the following test the assembly was still in GAC.

The test:
Using WiX 3.6, created a new setup project, with version 1.0.0.0 and
*MajorUpgrade *element default, containing a dll to install into GAC. 
Install this small setup. Windows Installer 5.0
Create version 2.0.0.0, change Product Id (*ProductCode*) and leave the
*MajorUpgrade *element default. The assembly for GAC remained the same.
Checked with Orca and *RemoveExistingProducts *was scheduled after
*InstallValidate *
Do a major upgrade.
The assembly remained in GAC.
In the log file there is something like:



Does that line from the log mean that the knowledge base article doesn't
apply anymore ?

Did I miss something and the *RemoveExistingProducts * action still needs to
be scheduled after *InstallFinalize *action so that the assemblies from GAC
are not removed after a major upgrade ?


Thanks,
Cristian

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingP
roducts-after-the-InstallFinalize-action-still-needed-so-that-Major-Upgrades-
don-t-re-tp7137858p7137858.html
Sent from the wix-users mailing list archive at Nabble.com.

-
-
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires 
that you delete it without acting upon or copying any of its contents, and we 
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, 
UK.


--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents