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. General Programming
  3. ATL / WTL / STL
  4. How to create and register two dlls with same name?(VS 2010)

How to create and register two dlls with same name?(VS 2010)

Scheduled Pinned Locked Moved ATL / WTL / STL
visual-studiohelptutorialquestion
6 Posts 4 Posters 3 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.
  • J Offline
    J Offline
    J_Me
    wrote on last edited by
    #1

    I have a problem where i have two dlls with same name. does changing CLSIDs of any one of it is advisable ? or any other alternate??

    jigar

    L A V 3 Replies Last reply
    0
    • J J_Me

      I have a problem where i have two dlls with same name. does changing CLSIDs of any one of it is advisable ? or any other alternate??

      jigar

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Obviously they would need different CLSIDs as there would be no way of distinguishing between them otherwise. The question remains: why?

      Veni, vidi, abiit domum

      J 1 Reply Last reply
      0
      • L Lost User

        Obviously they would need different CLSIDs as there would be no way of distinguishing between them otherwise. The question remains: why?

        Veni, vidi, abiit domum

        J Offline
        J Offline
        J_Me
        wrote on last edited by
        #3

        I have a situation where there are two applications A & B,using C.dll ,problem is that for A, development is frozen,while for B there is a huge overhaul expected in C.dll which will then break A,So either i need to create a new dll for B and rewrite same code of C.dll and do modification ,or i can just copy C.dll project and change its ProgGUID,CLSIDs and do modifications. indeed not a neat solution

        jigar

        L 1 Reply Last reply
        0
        • J J_Me

          I have a situation where there are two applications A & B,using C.dll ,problem is that for A, development is frozen,while for B there is a huge overhaul expected in C.dll which will then break A,So either i need to create a new dll for B and rewrite same code of C.dll and do modification ,or i can just copy C.dll project and change its ProgGUID,CLSIDs and do modifications. indeed not a neat solution

          jigar

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          The obvious answer is to create a copy of C.DLL source, probably by starting a new branch in your source control system. You can give it a different name and CLSID and use that for the development, while leaving the operational version intact. This is fairly standard procedure for any project.

          Veni, vidi, abiit domum

          1 Reply Last reply
          0
          • J J_Me

            I have a problem where i have two dlls with same name. does changing CLSIDs of any one of it is advisable ? or any other alternate??

            jigar

            A Offline
            A Offline
            Albert Holguin
            wrote on last edited by
            #5

            Having two dlls with the same name is not advisable in Windows.

            1 Reply Last reply
            0
            • J J_Me

              I have a problem where i have two dlls with same name. does changing CLSIDs of any one of it is advisable ? or any other alternate??

              jigar

              V Offline
              V Offline
              Vi2
              wrote on last edited by
              #6

              [Dynamic-Link Library Redirection] "To use DLL redirection, create a redirection file for your application. The redirection file must be named as follows: App_name.local. For example, if the application name is Editor.exe, the redirection file should be named Editor.exe.local. You must install the .local file in the application directory. You must also install the DLLs in the application directory."

              With best wishes, Vita

              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