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. C / C++ / MFC
  4. problem after .dll file changed to .ddl file in VS2005

problem after .dll file changed to .ddl file in VS2005

Scheduled Pinned Locked Moved C / C++ / MFC
questionhelp
6 Posts 4 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
    Shaileshhex
    wrote on last edited by
    #1

    Hi, I am migrating my code to VS2005 from VS2003. We have certain components which are .dll files but they are named as .ddl files .When i migrate to VS2005 and i open my client exe in dependency walker than the dependant .ddl file is shown as unavailable(with a question mark) in the walker. this mainly happens coz it has been renamed from .dll to .ddl(as per requirement). My question is , why does this happen in vs2005 only and how do i solve this?. Will it create problem at runtime?. NOTE: in VS2003 the file was seen available in the dependency walker. Replies are welcome Regards, Shailesh H

    S M 2 Replies Last reply
    0
    • S Shaileshhex

      Hi, I am migrating my code to VS2005 from VS2003. We have certain components which are .dll files but they are named as .ddl files .When i migrate to VS2005 and i open my client exe in dependency walker than the dependant .ddl file is shown as unavailable(with a question mark) in the walker. this mainly happens coz it has been renamed from .dll to .ddl(as per requirement). My question is , why does this happen in vs2005 only and how do i solve this?. Will it create problem at runtime?. NOTE: in VS2003 the file was seen available in the dependency walker. Replies are welcome Regards, Shailesh H

      S Offline
      S Offline
      sashoalm
      wrote on last edited by
      #2

      why do you need them to be called ddl files?

      There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition. Blaise Pascal

      S 1 Reply Last reply
      0
      • S sashoalm

        why do you need them to be called ddl files?

        There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition. Blaise Pascal

        S Offline
        S Offline
        Shaileshhex
        wrote on last edited by
        #3

        Well the reason for naming DDL is non technical. Its only to recognize the dll file thats the project requirement which we cannot change. thanks

        K 1 Reply Last reply
        0
        • S Shaileshhex

          Well the reason for naming DDL is non technical. Its only to recognize the dll file thats the project requirement which we cannot change. thanks

          K Offline
          K Offline
          KarstenK
          wrote on last edited by
          #4

          Check whether it isnt a writing mistake of some non-IT typ of manager. X| After all it is bad style :mad:

          Greetings from Germany

          S 1 Reply Last reply
          0
          • K KarstenK

            Check whether it isnt a writing mistake of some non-IT typ of manager. X| After all it is bad style :mad:

            Greetings from Germany

            S Offline
            S Offline
            Shaileshhex
            wrote on last edited by
            #5

            Its a bad style.. but it works in VS2003 and problems in VS2005. :)

            1 Reply Last reply
            0
            • S Shaileshhex

              Hi, I am migrating my code to VS2005 from VS2003. We have certain components which are .dll files but they are named as .ddl files .When i migrate to VS2005 and i open my client exe in dependency walker than the dependant .ddl file is shown as unavailable(with a question mark) in the walker. this mainly happens coz it has been renamed from .dll to .ddl(as per requirement). My question is , why does this happen in vs2005 only and how do i solve this?. Will it create problem at runtime?. NOTE: in VS2003 the file was seen available in the dependency walker. Replies are welcome Regards, Shailesh H

              M Offline
              M Offline
              Mark Salsbery
              wrote on last edited by
              #6

              Did the DLL project's linker option for output file get set to $(OutDir)\$(ProjectName).dll instead of what you want it to be? Mark

              Mark Salsbery Microsoft MVP - Visual C++ :java:

              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