Wcf service is not working when hosted in class library

Question

0.00/5 (No votes)

See more:

I am trying to implement a class library which is used to host a WCF service. It is containing a app.config. The same library I have used in a executable.
When I tried making the class library as executable it is running fine, service host is coming up.
When I refer the dll, and try to do ServiceHost.Open() I get following error:

{"Service 'ServiceClass' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element."}

I understood the app.config in dll is not accessible, I tried moving the config to app.config of executable it works.

Is there any way I can access app.config of the dll.

Please Help

What I have tried:

I tried looking for solution to this problem in many blogs, but no concrete solution

Posted 10-Aug-16 4:57am

Member 10095430

Updated 23-Aug-16 4:47am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

PeejayAdams · Answer 1 · 2016-08-23T04:47:00

Rather than creating an endpoint via the app.config, you can do it in code - something along the lines of:

C#

using System.ServiceModel.Description;
.
.
.
Uri baseAddress = new Uri("http://SomePath/MyService.svc");
.
BasicHttpBinding binding = new BasicHttpBinding();
EndpointIdentity identity = EndpointIdentity.CreateDnsIdentity("localhost");
EndpointAddress address = new EndpointAddress(baseAddress, identity);
.
MyService.MyServiceClient client = new MyService.MyServiceClient(binding, address);
client.DoSomething();