Did you ever encounter this dialog box when dealing with WCF services?
“The target assembly contains no service types. You may need to adjust the Code Access Security policy of this assembly.”
It might happen when you run application at debug time. It is highly annoying and time consuming (it pauses application for more than one minute without any apparent reason). But what does it mean and why does it happen?
When you create a project from a WCF project templates Visual Studio knows that this project is a WCF service and thus it offers two debug time helpers: WCF Service Host and WCF Client. These two guys are intended to help you with running and testing WCF services without writing any code – they just appear at debug time. So far so good. But why the annoying dialog?
The dialog in question means that you have a project, created using one of the WCF project templates, with an interface marked with ServiceContract attribute and in the same project you don’t have a class that implements this interface (perhaps you implemented that interface in another project). So, the WCF Service Host can’t find a suitable class to host the service and it complains through that dreaded dialog box. Note that WCF Service Host is pretty dumb and it is incapable of searching through other projects in same solution. OK, the solution is to stop running WCF Service Host or even better, instruct it which class implements the interface in question. Well, AFAIK the later is impossible while the former can be done through project file modification using notepad. Here is how:
Delete this line from your project file:
And you won’t see WCF Service Host or dreaded dialog anymore.
The question is, why didn’t [MS] think of these scenarios before?
BTW, if you just want to stop WCF Client from runing then delete this command line argument: /client:”WcfTestClient.exe”, created by WCF project template.