Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. personal assemblies, copy local to false

personal assemblies, copy local to false

Scheduled Pinned Locked Moved ASP.NET
helpdotnetquestion
5 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    tiziacaia
    wrote on last edited by
    #1

    hello! i loaded my private dll in my project references and after i set this property "copy local" to false (because is a shared library). when i try to run my application i get this error: "File or assembly name MyDll, or one of its dependencies, was not found." in some precedents projects I done this and work without register the dll in the gac. somebody can help me, please? thanks a lot! (if i set"copy local" to true all work correctly)

    M 1 Reply Last reply
    0
    • T tiziacaia

      hello! i loaded my private dll in my project references and after i set this property "copy local" to false (because is a shared library). when i try to run my application i get this error: "File or assembly name MyDll, or one of its dependencies, was not found." in some precedents projects I done this and work without register the dll in the gac. somebody can help me, please? thanks a lot! (if i set"copy local" to true all work correctly)

      M Offline
      M Offline
      minhpc_bk
      wrote on last edited by
      #2

      Hi there, You should not change this setting if your assembly is not placed in the GAC. Basically, the Visual Studio .NET build system copies any referenced assembly which has Copy Local=True to the application output folder (the bin folder), if you set it to False, then at runtime the application will fail to load the assembly from the bin folder as it's not there.

      T 2 Replies Last reply
      0
      • M minhpc_bk

        Hi there, You should not change this setting if your assembly is not placed in the GAC. Basically, the Visual Studio .NET build system copies any referenced assembly which has Copy Local=True to the application output folder (the bin folder), if you set it to False, then at runtime the application will fail to load the assembly from the bin folder as it's not there.

        T Offline
        T Offline
        tiziacaia
        wrote on last edited by
        #3

        thanks for the reply but i solved. i put in the project web.config these lines: and all work correctly without register the dll in the gac.

        1 Reply Last reply
        0
        • M minhpc_bk

          Hi there, You should not change this setting if your assembly is not placed in the GAC. Basically, the Visual Studio .NET build system copies any referenced assembly which has Copy Local=True to the application output folder (the bin folder), if you set it to False, then at runtime the application will fail to load the assembly from the bin folder as it's not there.

          T Offline
          T Offline
          tiziacaia
          wrote on last edited by
          #4

          thanks for the reply but i solved. i put in the project web.config these lines: and all work correctly without register the dll in the gac.

          M 1 Reply Last reply
          0
          • T tiziacaia

            thanks for the reply but i solved. i put in the project web.config these lines: and all work correctly without register the dll in the gac.

            M Offline
            M Offline
            minhpc_bk
            wrote on last edited by
            #5

            Hi there, Here you are using the codebase element with the absolute physical path to specify the location where the common language runtime can find your assembly, however, you may also need to care when you deploy your asp.net application to a product server.

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups