What you're asking is a little confusing. The CLR is backwards compatible; I can target 4.0 and use binaries that target version 3.5. I gain nothing from having the option to target a copy of your DLL that was built against version 4.0 of the framework... unless you are releasing both and updated version that targets 4.0 and still want to install a version that people targeting 3.5 can use.
If that is the case, and assuming your DLLs are strong named, they should be installed into the correct version of the GAC without any input from you. If the names are the same, you'll have to take the normal precautions for installing files with the same name (e.g., /bin/3.5 and /bin/4.0). Have you had issues with this? Is the install failing, or are you being proactive? If you haven't encountered an issue, I'd just install both and check /windows/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 against .NET 3.5 and 4.0 But what about if what I want is for the customer to be able to select via feature if they want to target the 3.5 or 4.0.? This is actually a customer scenario, so back to my question, is there any way in WIX or targetting one .NET versus other for GAC'ing purposes? > From: 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 target previous versions of the framework. > > -----Original Message----- > From: Andres Juarez [mailto:andresj_...@hotmail.com] > Sent: Monday, May 03, 2010 9:07 PM > To: wix-users@lists.sourceforge.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 and > 4.0 in the same machine and therefore we want to GAC the assembly against > both versions of the .NET. > > > > Is there a way of doing this in WIX? I do not see any other parameter > for the File element where to target different versions of the .NET. > What would if do with the > > Assembly=".net" if both versions of the framework are there already? > > > > Thanks > > Andres > > > > > > > > _________________________________________________________________ > Hotmail is redefining busy with tools for the New Busy. Get more from your > inbox. > http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAG > L:ON:WL:en-US:WM_HMP:042010_2 > ---------------------------------------------------------------------- > -------- _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ---------------------------------------------------------------------- > -------- _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users _________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1 ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
