Having issues with Referencing a DLL in a Solution with multiple Projects

Discussion in 'ASP .Net' started by pete@weruniq.com, Mar 6, 2007.

  1. Guest

    Greetings all,

    I am going to attempt to describe the issue that I am having in full.
    I apologize ahead of time that this may be a long posting, however, I
    have found no other solution to my problem.

    I am working with a VS2003 .NET1.1 Solution Project. The Solution
    contains 6 Projects:
    CEC_MT, CEC_UI, Common, CommonUI, FISCommon, and FISCommonUI.

    The Common and CommonUI are class library's that are for all intensive
    purposes static. We can't/shouldn't change any code in those
    projects. The Build Order is as follows: Common, CommonUI, FISCommon,
    CEC_MT, FISCommonUI, and CEC_UI.

    We currently have one workstation (CPU1) where this project compiles,
    runs, and debugs just fine. We are attempting to add an additional
    developer to work on this same project. We copied the Source Code
    from the working workstation to the new developers machine (CPU2).
    All running the same versions of all the controls, Stuido, and .NET.

    When we fire up Studio on CPU2, we immediately receive 147 error
    messages:

    'Public Overridable NotOverridable Property BackColor() As
    System.Drawing.Color' is declared in project
    'Janus.Windows.GridEX.dll', which is not referenced by project
    'CEC_UI.exe'.

    The object in question is located in C:\Program Files\FIS. We have
    approximately 10 objects that point to that directory, however, the
    error is ONLY on this one DLL, Janus.Windows.GridEX.dll.

    Nothing in the source code changed from CPU1 to CPU2. Trying to solve
    the issue, we redirected the References to point to the <project>\bin
    directory. That causes the error messages to go away, however, this
    doesn't help us because the references have to point to the C:\Program
    Files\FIS directory.

    We checked all of the Project Properties, and the Reference Paths all
    point to "C:\Program Files\FIS". Again, this same code works on CPU1,
    but not CPU2, and they "should" be identical builds.

    Can anyone provide some guidance or something for us to try? We're
    going on about 2 months of not getting past this. We only have one
    machine where this source code works.

    Thanks in advance.

    Pete Navarra.
    , Mar 6, 2007
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Stephen Miller
    Replies:
    0
    Views:
    1,645
    Stephen Miller
    Jun 24, 2003
  2. Andy G

    single solution-multiple projects

    Andy G, Jan 26, 2005, in forum: ASP .Net
    Replies:
    0
    Views:
    412
    Andy G
    Jan 26, 2005
  3. DLG
    Replies:
    4
    Views:
    517
  4. =?Utf-8?B?Q2hyaXM=?=
    Replies:
    0
    Views:
    585
    =?Utf-8?B?Q2hyaXM=?=
    Sep 15, 2005
  5. David Herbst
    Replies:
    1
    Views:
    505
    David Herbst
    Feb 1, 2006
Loading...

Share This Page