C# – WCF service unable to load referenced assemblies from the GAC

ciisnetvisual studiowcf

I've got a WCF service, hosted in IIS, which is built in Visual Studio. The WCF service library references a few other assemblies, which are part of the same Visual Studio solution.

I deploy all the assemblies to the GAC, then start a service client, and see it fail trying to resolve one of the referenced client assemblies. I've added a breakpoint in the WCF service contructor, and it appears to not try to load its referenced assemblies using qualified names (and thus not find them in the GAC). If I run an Assembly.Load in the immediate window, once breaked into the WCF contructor, within IIS, I'm able to load each of the missing dlls using qualified (publickeytoken and such) names.

Why does the CLR, or my service library, attempt to load the libraries using names only?

Best Answer

Try updating the IIS web app web.config that with the following

<compilation debug="true">
      <assemblies>
        <add assembly="MyWcfAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=AAAAAAAAAA"/>

From my experience this is needed sometimes when the dll isn't copied local and needs to be read from the GAC.

You also need to reload your app domain for your web page to use the latest assembly installed into your GAC. You can reload your app domain by doing an iisreset, touching the web.config or iis manager.

Related Solutions

C# – How to update the GUI from another thread

The simplest way is an anonymous method passed into Label.Invoke:

// Running on the worker thread
string newText = "abc";
form.Label.Invoke((MethodInvoker)delegate {
    // Running on the UI thread
    form.Label.Text = newText;
});
// Back on the worker thread

Notice that Invoke blocks execution until it completes--this is synchronous code. The question doesn't ask about asynchronous code, but there is lots of content on Stack Overflow about writing asynchronous code when you want to learn about it.

C# – MetadataException: Unable to load the specified metadata resource

This means that the application is unable to load the EDMX. There are several things which can cause this.

You might have changed the MetadataArtifactProcessing property of the model to Copy to Output Directory.
The connection string could be wrong. I know you say you haven't changed it, but if you have changed other things (say, the name of an assembly), it could still be wrong.
You might be using a post-compile task to embed the EDMX in the assembly, which is no longer working for some reason.

In short, there is not really enough detail in your question to give an accurate answer, but hopefully these ideas should get you on the right track.

Update: I've written a blog post with more complete steps for troubleshooting.

Best Answer

Related Solutions

C# – How to update the GUI from another thread

C# – MetadataException: Unable to load the specified metadata resource

Related Topic