引用Dll时未经授权的WCF（401）

Question

I have to shoe horn a call to a WCF service into a legacy VB6 app. To do this, I'm referencing ac# dll to call the wcf method. In the dll I'm setting the configuration as opposed to using a config file. The dll works when I run my unit tests, but once I execute it within the vb6 app, I get the following error:

System.Net.WebException: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest. WaitForReply(TimeSpan timeout) The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Negotiate,NTLM,Basic realm=[the ip]

The service is using basic authentication. In both scenarios I'm using the same url, username, and password. Here is the configuration I'm doing in code:

    BasicHttpBinding binding = new BasicHttpBinding
{
    SendTimeout = TimeSpan.FromMinutes(1),
    OpenTimeout = TimeSpan.FromMinutes(1),
    CloseTimeout = TimeSpan.FromMinutes(1),
    ReceiveTimeout = TimeSpan.FromMinutes(10),
    AllowCookies = false,
    BypassProxyOnLocal = false,
    HostNameComparisonMode = HostNameComparisonMode.StrongWildcard,
    MessageEncoding = WSMessageEncoding.Mtom,
    TextEncoding = System.Text.Encoding.UTF8,
    TransferMode = TransferMode.Buffered,
    UseDefaultWebProxy = true,
};

binding.Security.Mode = BasicHttpSecurityMode.TransportCredentialOnly;
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Basic;

var wcf = new [servicename](binding, new EndpointAddress([the url]));

if (wcf .ChannelFactory.Credentials != null)
{                
    wcf .ChannelFactory.Credentials.UserName.UserName = [the username];
    wcf .ChannelFactory.Credentials.UserName.Password = [the pw];
}

I can't figure out what is different when it gets executed by the VB6 app. Any input is appreciated.

Answer 1

The C# DLL is registered for com interop. I had assumed it was a byproduct of being called through vb6, but I took at step back and realized the wcf credentials were being provided correctly by the vb6, but the code path it followed in the dll was slightly different and they weren't being applied correctly.

Always seems to be that when things make no sense at all, some underlying assumption is wrong. Thanks for the suggestions.