NewsArchive
06-10-2013, 10:29 AM
PROBLEM: An increasing number of developers distribute .NET 4 assemblies and
one FAQ is 'Why does SetupBuilder not install my assembly into the Global
Assembly Cache (GAC)?'
SOLUTION: In .NET Framework 4.0, the GAC went through a few changes. To
avoid interference issues between CLR 2.0 and CLR 4.0, the GAC is now split
into private GACs for each runtime.
By default, SetupBuilder uses the ".NET Framework 2.0/3.0/3.5" registration
method to add .NET Assemblies into the GAC. To add a .NET 4 assembly into
the GAC, you have to use the "Set Active .NET Framework..." script function
to programmatically enable "Support .NET Framework 4.0" for your .NET 4
assemblies.
Friedrich
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 8 ready installations in minutes
--Official Comodo Code Signing and SSL Certificate Partner
one FAQ is 'Why does SetupBuilder not install my assembly into the Global
Assembly Cache (GAC)?'
SOLUTION: In .NET Framework 4.0, the GAC went through a few changes. To
avoid interference issues between CLR 2.0 and CLR 4.0, the GAC is now split
into private GACs for each runtime.
By default, SetupBuilder uses the ".NET Framework 2.0/3.0/3.5" registration
method to add .NET Assemblies into the GAC. To add a .NET 4 assembly into
the GAC, you have to use the "Set Active .NET Framework..." script function
to programmatically enable "Support .NET Framework 4.0" for your .NET 4
assemblies.
Friedrich
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 8 ready installations in minutes
--Official Comodo Code Signing and SSL Certificate Partner