Skip to main content

Installing to the GAC problem RRS feed

  • Question

  • We have an InstallShield installer that installed two components (two DLL's) to the GAC. It worked fine. We were requiring that .Net 3.5 be installed on the system.

    We upgraded our dll, DLL 'A', to use .NET 4.6.2 (and now require .Net 4.6.2 or greater to be installed on the system). DLL 'B' is Log4net.dll, from Apache (version 1.2). DLL A, has DLL B, as a dependency. When running the install now (on windows 7\10), DLL B will always be installed to the GAC, DLL A is never installed. If I change DLL B, to the latest version of Log4net.dll, which uses .net 4.5, (when installing on a system that has .net 4.6 or 4.7), neither dll gets installed to the GAC.

    If you use the latest version of gacutil, on the command line, it will install DLL A to the GAC.

    I am not a product developer (I take care of the installer), so I am theorizing here. My theory is that because DLL A has a dependency on DLL B (the older version that does get installed to the GAC), that both dll's need to be set to use .NET 4.6.2, and because DLL A cannot find the dependency with the same .NT version, DLL A does not get installed to the GAC.

    Or, is there something else going on here?

    Note, Log4net.dll does not have a version that uses a .NET version higher than 4.5, so, even if I am correct about both dll's needing to use the same .net version, we are still screwed?
    Thursday, April 12, 2018 11:14 AM

All replies


    The new 4.6.,2 dll was being the 4.0 GAC, in C:\Windows\Microsoft.NET\assembly
    Thursday, April 12, 2018 7:22 PM
  • Hi,

    Thank you for posting here.

    As far as I know that the Apache log4net library is a tool to help the programmer output log statements to a variety of output targets.

    log4net is a port of the excellent Apache log4j framework to the Microsoft .NET runtime.  I think that it is third product, you can post the issue on Apache support website for help.

    Best Regards,


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Friday, April 13, 2018 6:52 AM