4.0) then the 3.5 assemblies would be in one feature and
> the 4.0 in the other.
>
> Phil Wilson
>
> -Original Message-
> From: Andres Juarez [mailto:andresj_...@hotmail.com]
> Sent: Tuesday, May 04, 2010 10:30 AM
> To: wix-users@lists.sourceforge.net
> Subjec
Original Message-
From: Andres Juarez [mailto:andresj_...@hotmail.com]
Sent: Tuesday, May 04, 2010 10:30 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to GAC an assembly against .NET 3.5 and 4.0
But what about if what I want is for the customer to be able to select
assembly and Windows\Microsoft.NET\assembly to make sure they
both installed to the respective gacs.
-Original Message-
From: Andres Juarez [mailto:andresj_...@hotmail.com]
Sent: Tuesday, May 04, 2010 1:30 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to GAC an assembly agai
: wsulli...@softdocs.com
> To: wix-users@lists.sourceforge.net
> Date: Tue, 4 May 2010 06:09:41 -0400
> Subject: Re: [WiX-users] How to GAC an assembly against .NET 3.5 and 4.0
>
> This is something you don't have to worry about. Version 4 of the CLR will
> handle assemblies that
e.net
Subject: [WiX-users] How to GAC an assembly against .NET 3.5 and 4.0
Hi All,
We have been GAC'ing an assembly against .NET 3.5 by making use of the
Assembly=".net" attribute. That works well.
Now we need to support cases where the end customer might have .NET 3.5
Hi All,
We have been GAC'ing an assembly against .NET 3.5 by making use of the
Assembly=".net" attribute. That works well.
Now we need to support cases where the end customer might have .NET 3.5 and 4.0
in the same machine and therefore we want to GAC the assembly against both
versions
6 matches
Mail list logo
