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 Studio
  4. Setup/Deployment Warning: Unable to find dependency... [solved]

Setup/Deployment Warning: Unable to find dependency... [solved]

Scheduled Pinned Locked Moved Visual Studio
csharpannouncementc++wcfsysadmin
3 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.
  • C Offline
    C Offline
    Calla
    wrote on last edited by
    #1

    Hi, I'm trying to get a Setup Project to build, and it does but with two Warnings saying:

    "Unable to find dependency 'MY_WCF_SERVICE_LIBRARY' (Signature='(null)' Version='1.0.0.0' of Assembly 'My_WinForm_Assembly.exe'...
    "Unable to find dependency 'MY_WCF_SERVICE_LIBRARY' (Signature='(null)' Version='1.0.0.0' of Assembly 'My_WCF_ServiceHost_Assembly.exe'...

    The solution also contains some C++ projects and my three .NET assemblies:* WCF Service Library [called 'MY_WCF_SERVICE_LIBRARY' here]

    • WCF Service Host [called 'My_WCF_ServiceHost_Assembly.exe' here]

    • WinForm client application [called 'My_WinForm_Assembly.exe' here] using the WCF Service Library (referencing it) and consuming the WCF Service (which also references the WCF Library). Since our product not only contains .NET assemblies we build specifically for 32 and 64 bits OS (including my assemblies). So in the "Setup 32" project I have added the assemblies of the release build of my 32 bits .NET assemblies and in my "Setup 64" project the assemblies built for 64 bit. The Warning message shows up for both my 32 and 64 bit Setup project, and as you can see it's the WinForm and WCF Service host project's that says they can't find the WCF Service Library. Does anyone know why I get these messages and how to configure my Setup to get rid of them? Additional info: I'm using VS2008, Windows XP SP3 (32 bit machine) and .NET 3.5

      modified on Wednesday, October 21, 2009 5:02 AM

    C P 2 Replies Last reply
    0
    • C Calla

      Hi, I'm trying to get a Setup Project to build, and it does but with two Warnings saying:

      "Unable to find dependency 'MY_WCF_SERVICE_LIBRARY' (Signature='(null)' Version='1.0.0.0' of Assembly 'My_WinForm_Assembly.exe'...
      "Unable to find dependency 'MY_WCF_SERVICE_LIBRARY' (Signature='(null)' Version='1.0.0.0' of Assembly 'My_WCF_ServiceHost_Assembly.exe'...

      The solution also contains some C++ projects and my three .NET assemblies:* WCF Service Library [called 'MY_WCF_SERVICE_LIBRARY' here]

      • WCF Service Host [called 'My_WCF_ServiceHost_Assembly.exe' here]

      • WinForm client application [called 'My_WinForm_Assembly.exe' here] using the WCF Service Library (referencing it) and consuming the WCF Service (which also references the WCF Library). Since our product not only contains .NET assemblies we build specifically for 32 and 64 bits OS (including my assemblies). So in the "Setup 32" project I have added the assemblies of the release build of my 32 bits .NET assemblies and in my "Setup 64" project the assemblies built for 64 bit. The Warning message shows up for both my 32 and 64 bit Setup project, and as you can see it's the WinForm and WCF Service host project's that says they can't find the WCF Service Library. Does anyone know why I get these messages and how to configure my Setup to get rid of them? Additional info: I'm using VS2008, Windows XP SP3 (32 bit machine) and .NET 3.5

        modified on Wednesday, October 21, 2009 5:02 AM

      C Offline
      C Offline
      Calla
      wrote on last edited by
      #2

      I found the solution to my problem, and I'll post it here in case someone does the same mistake as I did.. In my Setup project under File System I had choose to add Assembly of my WinForm instead of Project Output, and I repeated this mistake for all of my three .NET assemblies. By adding them to the File System as Project Output instead of Assembly made the Warnings go away. :)

      1 Reply Last reply
      0
      • C Calla

        Hi, I'm trying to get a Setup Project to build, and it does but with two Warnings saying:

        "Unable to find dependency 'MY_WCF_SERVICE_LIBRARY' (Signature='(null)' Version='1.0.0.0' of Assembly 'My_WinForm_Assembly.exe'...
        "Unable to find dependency 'MY_WCF_SERVICE_LIBRARY' (Signature='(null)' Version='1.0.0.0' of Assembly 'My_WCF_ServiceHost_Assembly.exe'...

        The solution also contains some C++ projects and my three .NET assemblies:* WCF Service Library [called 'MY_WCF_SERVICE_LIBRARY' here]

        • WCF Service Host [called 'My_WCF_ServiceHost_Assembly.exe' here]

        • WinForm client application [called 'My_WinForm_Assembly.exe' here] using the WCF Service Library (referencing it) and consuming the WCF Service (which also references the WCF Library). Since our product not only contains .NET assemblies we build specifically for 32 and 64 bits OS (including my assemblies). So in the "Setup 32" project I have added the assemblies of the release build of my 32 bits .NET assemblies and in my "Setup 64" project the assemblies built for 64 bit. The Warning message shows up for both my 32 and 64 bit Setup project, and as you can see it's the WinForm and WCF Service host project's that says they can't find the WCF Service Library. Does anyone know why I get these messages and how to configure my Setup to get rid of them? Additional info: I'm using VS2008, Windows XP SP3 (32 bit machine) and .NET 3.5

          modified on Wednesday, October 21, 2009 5:02 AM

        P Offline
        P Offline
        parthibab
        wrote on last edited by
        #3

        I recently faced the same problem and found the solution on my own which worked for me. I just checked the references list in the solutions explorer and found that there were two or more dependencies attached of the same reference. Eg. Assembly.dll is the main reference, but another reference like Assembly.design.dll was also attached. So i removed the Assembly.design.dll that solved the problem Hope this help:-)

        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