Results 1 to 6 of 6

Thread: [2008] Properly reference 3rd party dlls for proper deployment

  1. #1

    Thread Starter
    Fanatic Member
    Join Date
    Jun 2008
    Posts
    515

    [2008] Properly reference 3rd party dlls for proper deployment

    I am having problems properly referencing 3rd party dlls.

    Where should they be stored in a project and how should they be referenced so that clickonce will properly deploy.

    Thanks

  2. #2

    Thread Starter
    Fanatic Member
    Join Date
    Jun 2008
    Posts
    515

    Re: [2008] Properly reference 3rd party dlls for proper deployment

    anyone ?

  3. #3
    Fanatic Member Clanguage's Avatar
    Join Date
    Jan 2008
    Location
    North Carolina
    Posts
    659

    Re: [2008] Properly reference 3rd party dlls for proper deployment

    The references should end up in the bin directory of your project and should be included with ClickOnce automatically. What kind of trouble are you having?
    CLanguage;
    IF Post = HelpFull Then
    RateMe
    Else
    Say("Shut UP")
    End If
    DotNet rocks
    VB 6, VB.Net 2003, 2005, 2008, 2010, SQL 2005, WM 5.0,ahem ?OpenRoad?

  4. #4

    Thread Starter
    Fanatic Member
    Join Date
    Jun 2008
    Posts
    515

    Re: [2008] Properly reference 3rd party dlls for proper deployment

    Does the 3rd party dll have to first be copied to project's Bin directory and then I set the reference to that dll in the bin directory ?

    What happens if the original dll is on a removable drive.

    When I go back into my project | Properties and tab references...

    I still find the dll referenced to the removable drive's path...

  5. #5
    Fanatic Member Clanguage's Avatar
    Join Date
    Jan 2008
    Location
    North Carolina
    Posts
    659

    Re: [2008] Properly reference 3rd party dlls for proper deployment

    1 Sorry I was away. You should not have to bring the dll manually but I
    2 guess if you want to make sure it is included it will not hurt.
    3 Visual Studio copies the dll to the bin from wherever it is located.
    4 I think that it is done in the click once. If not copy it to the bin and point your reference to it.
    Hope this helps
    CLanguage;
    IF Post = HelpFull Then
    RateMe
    Else
    Say("Shut UP")
    End If
    DotNet rocks
    VB 6, VB.Net 2003, 2005, 2008, 2010, SQL 2005, WM 5.0,ahem ?OpenRoad?

  6. #6

    Thread Starter
    Fanatic Member
    Join Date
    Jun 2008
    Posts
    515

    Re: [2008] Properly reference 3rd party dlls for proper deployment

    Thanks. I cannot figure out why when a ref is set to a dll on a removable drive, project reference remains set to that path.

    It results in failure when the drive is not available.

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