c# - Strange Component Registration error with Castle Windsor WcfFacility -


I try to convert WCF to my existing site to communicate with my services on another box I am doing Currently I use automatic registration to wire-up my services directly when I try to use Windsor's WCfFacility, I get a component registration exception on one of my interfaces, which I have to register The error I am trying is given below, it is only on a special interface, all other interfaces work properly and are coded in the same way.

  type demo.Ifuseva is the essence of the essence. As such, it is not possible to install demo.Ifuseva service as a service.  

I have another Windows form that I have changed from the same service to use WCF and It works 100%.

  Container. Registered (Component.For & lt; IFooService & gt; (). Nominated ( 

I register with WCF services (both windows and web applications) using the following code. "FooService") .ActAs (New Default ClientModel {Endpoint = WCfEndPoint.BoundTo (New BasicHTPBending ()). ("Http: //localhost/services/fooservice.svc"))));

Interface service is marked with contract and operation contract attributes, and similar to all other people.

I do not know why Windsor is seeing it as an abstract class, but the other is recording correctly.

Any thoughts?

I have solved this issue, it seems that I can not Destroys the WCFFacility on the web app, but still it was on the Windows app, which explains why it was working there. I'm an idiot, it seems ... oh well.

Hope this will help anyone running the exception and that's stupid like me :)

Thanks anyway for help.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -