Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Registering DLLs in vb.net for idiots

Options
  • 25-11-2008 5:15pm
    #1
    mountainyman
    Closed Accounts Posts: 2,268 ✭✭✭


    Registering DLLs in vb.net for idiots:

    Does anyone know any good sources for information on registering DLLs in vb.net


Comments

  • Options
    #2
    kayos
    Registered Users Posts: 2,494 ✭✭✭kayos


    /facepalm

    VB.NET does not produce COM DLL's.....

    Unless your talking about placing them in the GAC?


  • Options
    #3
    mountainyman
    Closed Accounts Posts: 2,268 ✭✭✭mountainyman


    What do i do with .net DLLs that are in the GAC and that it still can't find?
      Message="Could not load file or assembly 'Encryption, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified."
  Source=Login"
    It is a DLL being called from another DLL


  • Options
    #4
    stevenmu
    Moderators, Society & Culture Moderators Posts: 9,689 Mod ✭✭✭✭stevenmu


    First make sure it is in there, use "gacutil /l" to list the contents of the GAC, or "gacutil /l encryption" to display just that entry.

    That'll also let you check the version and if the PublicKeyToken is really null.

    How have you added the reference to the DLL?


  • Options
    #5
    mountainyman
    Closed Accounts Posts: 2,268 ✭✭✭mountainyman


    I am doing a class in this exact subject.
    I will sson be an expert.


  • Options
    #6
    Ginger
    Registered Users Posts: 2,931 ✭✭✭Ginger


    kayos wrote: »
    /facepalm

    VB.NET does not produce COM DLL's.....

    Unless your talking about placing them in the GAC?

    You can produce COM visible .NET DLLs, meanthing that they can be used by other applications that cant natively use .NET

    For example using regasm on a .NET assembly adds the information to the registry to allow it be used like a COM object.

    In relation to loading an assembly,

    Have a look at the following

    http://blogs.msdn.com/junfeng/articles/229648.aspx
    http://support.microsoft.com/?id=317540
    http://blogs.msdn.com/junfeng/articles/229649.aspx


  • Advertisement
Advertisement