NewsArchive
06-22-2011, 12:23 PM
..NET Developers:
The following interesting support request came in this morning. The problem
was that two .NET assemblies did not install into the Global Assembly Cache
(GAC). Other assemblies were installed OK. The two assemblies that did not
make it into the GAC were .NET 4 based!
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.
Of course, SetupBuilder 7.4 can handle this scenario. By default,
SetupBuilder uses the ".NET Framework 2.0/3.0/3.5" registration method to
add .NET Assemblies into the GAC. The solution is to use the "Set Active
..NET Framework..." script function to programmatically enable "Support .NET
Framework 4.0" for the two (.NET 4) assemblies.
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
SetupBuilder is Windows 7 installation -- "point. click. ship"
-- Official Comodo Code Signing and SSL Certificate Partner
The following interesting support request came in this morning. The problem
was that two .NET assemblies did not install into the Global Assembly Cache
(GAC). Other assemblies were installed OK. The two assemblies that did not
make it into the GAC were .NET 4 based!
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.
Of course, SetupBuilder 7.4 can handle this scenario. By default,
SetupBuilder uses the ".NET Framework 2.0/3.0/3.5" registration method to
add .NET Assemblies into the GAC. The solution is to use the "Set Active
..NET Framework..." script function to programmatically enable "Support .NET
Framework 4.0" for the two (.NET 4) assemblies.
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
SetupBuilder is Windows 7 installation -- "point. click. ship"
-- Official Comodo Code Signing and SSL Certificate Partner