Dependency practices

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Earl

    #1

    Dependency practices

    Is it poor practice to have one custom library depend on another custom
    library? For example, my data manipulation library depends on my replication
    library, which in turn pulls serial data out of an XML file.


  • Herfried K. Wagner [MVP]

    #2
    Re: Dependency practices

    "Earl" <brikshoe@newsg roups.nospam> schrieb:[color=blue]
    > Is it poor practice to have one custom library depend on another custom
    > library? For example, my data manipulation library depends on my
    > replication library, which in turn pulls serial data out of an XML file.[/color]

    Not necessarily.

    --
    M S Herfried K. Wagner
    M V P <URL:http://dotnet.mvps.org/>
    V B <URL:http://classicvb.org/petition/>

    Comment

    • Earl

      #3
      Re: Dependency practices followup question

      Thanks Herfried ... that was what I suspected "it depends".

      Followup question: if I change the contents of a referenced custom .dll, do
      I have to remove and re-add the reference in the referring project or will
      it pick up the version change?

      "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
      news:eShbWsUUFH A.2172@tk2msftn gp13.phx.gbl...[color=blue]
      > "Earl" <brikshoe@newsg roups.nospam> schrieb:[color=green]
      >> Is it poor practice to have one custom library depend on another custom
      >> library? For example, my data manipulation library depends on my
      >> replication library, which in turn pulls serial data out of an XML file.[/color]
      >
      > Not necessarily.
      >
      > --
      > M S Herfried K. Wagner
      > M V P <URL:http://dotnet.mvps.org/>
      > V B <URL:http://classicvb.org/petition/>[/color]


      Comment

      • Herfried K. Wagner [MVP]

        #4
        Re: Dependency practices followup question

        "Earl" <brikshoe@newsg roups.nospam> schrieb:[color=blue]
        > Followup question: if I change the contents of a referenced custom .dll,
        > do I have to remove and re-add the reference in the referring project or
        > will it pick up the version change?[/color]

        I suggest to add both projects to the same solution and use a project
        reference instead of referencing the DLL directly.

        --
        M S Herfried K. Wagner
        M V P <URL:http://dotnet.mvps.org/>
        V B <URL:http://classicvb.org/petition/>

        Comment

        • Earl

          #5
          Re: Dependency practices followup question

          Thanks for the advice, unfortunately there are business reasons why the .dll
          files must be kept separate. It appears right now that I have to remove the
          reference and re-reference when I make a change.

          "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
          news:%23t45E8aU FHA.4056@TK2MSF TNGP15.phx.gbl. ..[color=blue]
          > "Earl" <brikshoe@newsg roups.nospam> schrieb:[color=green]
          >> Followup question: if I change the contents of a referenced custom .dll,
          >> do I have to remove and re-add the reference in the referring project or
          >> will it pick up the version change?[/color]
          >
          > I suggest to add both projects to the same solution and use a project
          > reference instead of referencing the DLL directly.
          >
          > --
          > M S Herfried K. Wagner
          > M V P <URL:http://dotnet.mvps.org/>
          > V B <URL:http://classicvb.org/petition/>[/color]


          Comment

          Working...