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. Visual Basic
  4. DLL Problem

DLL Problem

Scheduled Pinned Locked Moved Visual Basic
helptutorial
2 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.
  • S Offline
    S Offline
    Sasmi
    wrote on last edited by
    #1

    :mad:Hi Guys, I Have a dll name 'XYZ.dll' which i use in my project call 'ABC' and install it on users pc and i use same dll 'XYZ.dll' (with some major changes) in my another project call 'PQR' if i install this pqr on users PC i found it overwrite the first one dll which is use in 'ABC' project. can any one help me regarding this i am first time using this dll funda in vb6. if any one give me detail idea about 'How to use dll' it will really great for me. Thanks in advanced Sasmi

    C 1 Reply Last reply
    0
    • S Sasmi

      :mad:Hi Guys, I Have a dll name 'XYZ.dll' which i use in my project call 'ABC' and install it on users pc and i use same dll 'XYZ.dll' (with some major changes) in my another project call 'PQR' if i install this pqr on users PC i found it overwrite the first one dll which is use in 'ABC' project. can any one help me regarding this i am first time using this dll funda in vb6. if any one give me detail idea about 'How to use dll' it will really great for me. Thanks in advanced Sasmi

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      I assume this is a COM dll, otherwise you could just put the dlls in the directories with the apps and it would be fine. You've done the wrong thing, and there's no easy way around it. If you're going to change a COM dll, you need to generate a new GUID so you have a new version. Either way, you should never break existing functionality, only add new functionality. In .NET, dlls are not registered, and are just loaded from the local directory. This change was made because the recommended way to use COM would work fine, but too many people just didn't bother to do it properly/thoughtfully.

      Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog

      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