Results 1 to 4 of 4

Thread: Library Deployment

  1. #1

    Thread Starter
    Powered By Medtronic dbasnett's Avatar
    Join Date
    Dec 2007
    Location
    Jefferson City, MO
    Posts
    9,897

    Library Deployment

    We have a library that provides read only functionality to some databases. This library depends on two othe libraries. All works as expected when testing with a sample application.

    My question is how to provide developers that work in other agencies this library / libraries. What I have done so far is to make copies of all three libraries and give that to the developers. That seems to work, but I don't know why.

    What I don't understand is how the references are resolved. Any insight would be appreciated, especially if it means I don't have to worry
    My First Computer -- Documentation Link (RT?M) -- Using the Debugger -- Prime Number Sieve
    Counting Bits -- Subnet Calculator -- UI Guidelines -- >> SerialPort Answer <<

    "Those who use Application.DoEvents have no idea what it does and those who know what it does never use it." John Wein

  2. #2
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    111,221

    Re: Library Deployment

    A .NET assembly basically looks in the same folder and in the GAC by default for any assemblies it references, so if your developers are adding references to the DLLs you provide and setting Copy Local to True for those references (which should happen by default) then they will end up in the same folder as the EXE and everything will just work.

    A slightly better option might be to create a NuGet package and host it on your network. They can then add that package in VS and it will be downloaded from the appropriate source and everything will just work. The nice thing about NuGet is that it makes it easy to package dependencies and also provide updates.
    Why is my data not saved to my database? | MSDN Data Walkthroughs
    VBForums Database Development FAQ
    My CodeBank Submissions: VB | C#
    My Blog: Data Among Multiple Forms (3 parts)
    Beginner Tutorials: VB | C# | SQL

  3. #3

    Thread Starter
    Powered By Medtronic dbasnett's Avatar
    Join Date
    Dec 2007
    Location
    Jefferson City, MO
    Posts
    9,897

    Re: Library Deployment

    Quote Originally Posted by jmcilhinney View Post
    A .NET assembly basically looks in the same folder and in the GAC by default for any assemblies it references, so if your developers are adding references to the DLLs you provide and setting Copy Local to True for those references (which should happen by default) then they will end up in the same folder as the EXE and everything will just work.

    A slightly better option might be to create a NuGet package and host it on your network. They can then add that package in VS and it will be downloaded from the appropriate source and everything will just work. The nice thing about NuGet is that it makes it easy to package dependencies and also provide updates.
    Thanks John.
    My First Computer -- Documentation Link (RT?M) -- Using the Debugger -- Prime Number Sieve
    Counting Bits -- Subnet Calculator -- UI Guidelines -- >> SerialPort Answer <<

    "Those who use Application.DoEvents have no idea what it does and those who know what it does never use it." John Wein

  4. #4
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    111,221

    Re: Library Deployment

    If you're interested in NuGet, you might start here:

    https://theroks.com/create-and-host-...uget-packages/
    Why is my data not saved to my database? | MSDN Data Walkthroughs
    VBForums Database Development FAQ
    My CodeBank Submissions: VB | C#
    My Blog: Data Among Multiple Forms (3 parts)
    Beginner Tutorials: VB | C# | SQL

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width