Mike,

Thanks for the answer.

The assembly's version is not meant to be changed in the future. It is
currently being developed by a 3rd party and once finished- we will
install and use it as is. My worry is regarding the development and QA
phase, I would really like them to be able to get updated assembly
versions upon upgrade. When the software is released I'm much less
worried, since the assembly will be final and won't change.

Now that you say that it is not updated- that gets me worried.

We're not doing major upgrades, only minor updated (changing only the
package ID).

 

The demand to put it in the GAC came from the developing team (other
team than mine, but I'm in charge of the installation of their product
as well).

The assembly we install requires .Net 2.0, don't know if that matters...
we don't mind having .NET installed on our kit-building machines. 

 

What is the AssemblyFileVersion attribute? What does it do/mean?

I'll search for an answer through the web, but I've learned that
sometimes the answers I get here are much better.

 

Thanks a lot,

MP. 

 

________________________________

From: Mike Dimmick [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 14, 2008 11:57 PM
To: Michal Peled; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Installing an assembly to the GAC - how does it
actinupdates?

 

GAC assemblies are inherently side-by-side, if you change the assembly
version. However, this means updating the clients or distributing
publisher policy (or configuration files) to redirect clients to the
newer version.

 

If you don't change the assembly version, an existing copy of the
assembly is not updated. The exception is if you've indicated, using the
-fv switch to Light, that you want the file version to be taken into
account (AssemblyFileVersion attribute). This support requires at least
.NET 1.1 SP1 to be installed.

 

If you're doing a major upgrade, using RemoveExistingProducts, and the
old version of your product is the only product referencing the copy in
the GAC, the old version of the assembly may be removed before the
decision to install the new one is taken (if RemoveExistingProducts is
scheduled in either of the first two locations listed in the
documentation), so it works by accident.

 

If your assembly isn't being shared between multiple products, what's it
doing in the GAC?

 

-- 

Mike Dimmick

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michal
Peled
Sent: 14 February 2008 13:14
To: Michal Peled; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Installing an assembly to the GAC - how does it
actinupdates?

 

Sorry, forget the question... I just saw I can look in
c:\windows\assembly, and see the "last modified" date in the assembly
properties (based on that- the assembly gets updated).

That's what happens when you give a ansi C girl to handle .NET...  :)

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michal
Peled
Sent: Thursday, February 14, 2008 2:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installing an assembly to the GAC - how does it act
inupdates?

 

Hi all,

I have a component with this line:

 

<File Id="yadayada" Name=" yadayada.dll"  DiskId="1" Assembly=".net"
Source="c:\blabla\ yadayada.dll" KeyPath="yes"/>

 

That installs "YadaYada" to the GAC.

 

It seems to work fine, by I'm not fully convinced that minor updates of
our product update the assembly in the GAC as well.

The assembly file (DLL) is being changed quite regularly nowadays (it's
in development phase), but we don't change its version or name or
anything, just the code.

Does the assembly in the GAC gets replaced with the new one when we do
repair/minor updates? Or is it considered as "already exist" and
ignored?

If so- what is the best way to force the updated assembly to replace the
old one?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to