I have one Wcf service project and in it many services called Service1, Service2 etc.
However, only Service1 is running. Why is this and how to resolve it?
This is a bit vague description of your problem, but maybe this will help. I did a post on how to host many WCF services in one windows service. If it doesn't help, check that your ABC(address, binding and contract) are set correctly.
Related
I'm building a self-hosted service to be consumed by Silverlight. This service is not a straight Wcf service, but it uses HttpListener to implement a streaming service for Silverligt. To mkae it accessible by Silverlight, I've created another service (that is a Wcf service) to serve the clientaccesspolicy.xml file.
My problem is that once my clientaccesspolicy service is registered at http://localhost:9001 I cannot access my streaming service that is listening at http://localhost:9001/silverlightstream.
I've a couple of other Wcf services registered at http://localhost:9001/xxx which can seamlessly coexist with the clientaccesspolicy service.
What do I need to do to get the streaming service to work together with the clientaccesspolicy service?
Thanks in advance for your help.
I've answered a similar question before, I don't know how much it fits your situation, but it does look like it might help you out a little:
How can I host a Silverlight 4 application in a WPF 4 application?
In my project, I took it further and delivered the html/xap files via said self hosted service (so as not to require IIS, as IIS was a bit too much bloat for what I required).
I'm newbie in WCF. I have some questions need to be answered.
Can I use WCF to make a simple chat application from a client to a client (via WCF Service) ?
I have tried follow many examples, And i got a problem. I don't think that IIS need to be installed when i using WCF Selft Hosted, right ?
Sorry about my English !
You don't need IIS for self-hosted WCF services. Look at the ServiceHost class.
Yes, you can make a chat application (client to client) using a service "in the middle". The clients would have to register with the service and then a callback contract should do the job.
I'm having an issue with a net.tcp WCF windows service int .NET 4.0 where it looks like my mex for a particular endpoint is too large. There is no problem at all connecting directly to the endpoint. I created a WCF RoutingService to allow someone outside our private network to connect to my internal WCF service. Getting the mex information through the RoutingService fails.
My WCF service has about 7 endpoints, and the WCF RoutingService is routing all of them, but only the large one (with 17 methods) is having the problem.
I found this link below which explains how to fix the problem when failing to connect directly to the mex endpoint
http://blogs.msdn.com/b/distributedservices/archive/2009/05/07/too-many-operations-or-methods-in-wcf-service-causes-the-metadataexchange-fail.aspx
But it talks about creating an endpoint in svcutil.exe.config with a contract of IMetadataExchange. The RoutingService endpoint I'm having a problem with is using the contract System.ServiceModel.Routing.IRequestReplyRouter, so I don't know if I need to configure the svcutil.exe.config file slightly differently. I've tried all sorts of combinations but couldn't get anything to work. I'm not even sure where I need to put the svcutil.exe.config file for the RoutingService WCF service to pick it up, or even if it needs one.
Does anybody know of a better solution, or a link which might provide help for when a RoutingService is involved?
Does anyone know how to host a WCF Data Service (or OData) inside IIS7? I'm seeing lots of articles about hosting WCF, but none specific to WCF Data Service.
Thank you very much.
Hosting a WCF Data Service in IIS is actually the default option.
Its a pretty easy 3 step process:
Create a new WebApplication project (or re-use an existing one)
Add a WCF Data Service to the project
Deploy to your IIS server
Step 3 is just the standard process for deploying a WebApplication to IIS.
A WCF Data Service is just a WCF (REST) service, with some additional out-of-the-box functionality added in.
It has a *.svc file and all - it will be hosted very much the same as a "regular" WCF REST service.
So all the articles you see about WCF REST should really apply to WCF Data Services as well - or are you experiencing some difficulties with something specifically??
Can anyone please explain me how to discover a WCF service if you do not know the type of the service Interface.
I am very new to WCF services and I need to write an application to discover some WCF services hosted in the subnet.
I found that you need to specify the service interface in inorder to create a FindCriteria object.
FindCriteria criteria new FindCriteria(typeof(IService1)
Please explain me how this works generally.
This is not how discovery works. WCF discovery is based on WS-Discovery protocol. The protocol is for discovering service with known contract = discovery finds address of the service with known contract. If you don't know the contract you can't use WCF discovery. This is explained in WCF Discovery overview.
If you don't know the contract you don't know what service you are looking for so how would you like to automatically discover it and how would you like to use it?
You can create an empty findcriteria: new FindCriteria().
This will find all discoverable service endpoints.
If you just want to take a look at the service operations, you can use the wcf test client application usually located in "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\"
All you'll need is the address to the service and you'll be able to try its operations
You can define scopes in the service behavior to "classify" your service and define the scope and scopematch on the findcriteria for partial or full or none match...