.NET remoting: System references wrong .NET dll, but how to cure ?

Posted by Quandary on Stack Overflow See other posts from Stack Overflow or by Quandary
Published on 2010-05-31T14:24:08Z Indexed on 2010/05/31 17:03 UTC
Read the original article Hit count: 178

Filed under:
|
|
|

Question: I defined an interface like below. The problem now is, that when I add the dll (API.dll) as reference in an asp.net project, it references a wrong API.dll, though I referenced the correct dll.

In turn, it doesn't find GetLDAPlookup, but there is another method that is not in defined here, but in an older version of API.dll... I rebuilt the dll I referenced, so it is definitely the latest version that I added as reference.

Do I have to add another GUID, or something ?

Imports System.Runtime.InteropServices

Namespace RemoteObject




''' <summary>
''' Defines server interface which will be deployed on every client
''' </summary>
''' 
<GuidAttribute("921DE547-32FA-40BB-961A-EA390B7AE27D")> _
Public Interface IServerMethods


    ''' <summary>
    ''' Function to call the server from the client
    ''' </summary>
    ''' <param name="strMessage">Some text</param>
    ''' 
    Sub ServerPrint(ByVal strMessage As String)

    ''' <summary>
    ''' Function to call the server from the client
    ''' </summary>
    ''' <param name="strMessage">Some text</param>
    ''' <returns>Some interesting text</returns>
    ''' 
    Function GetLDAPlookup(ByVal strMessage As String) As System.Data.DataSet

End Interface

End Namespace

© Stack Overflow or respective owner

Related posts about c#

Related posts about vb.net