kala-tamin Exposing structure - WCF web service


Exposing structure - WCF web service



I have a seperate assembly ( reference by WebService) in which I have created a class ( Let's say ABC ) and a collection of that class ( ABCCollection : IList where T:ABC ). Now when I build the proxy files (output.config and Service1.cs) then the defienation of these two classes are not exposed. Instead the ABCCollection is exposed in Servic1.cs is like ABCCollection4IP3 .

Please let me know the possible cause for this issues..




WCF: What exactly does IsInitiating do?

1:



Publishing schema as wcf service trouble
They are not meant to be the same type.


What are my binding options for a self hosted cross domain WCF service with remote thick clients?
This is by design.


How do you specify a message label when using WCF and NetMsmqBinding?
Consider how it would work if your service were in .NET and your client in Java.


WCF Proxy Generation
They would clearly be two different types..
WCF - contract-first vs. code-first - how to document easily / properly?


Read Http Cookie from Request Stream In a WCF Service


WAS hosting of queues

2:


A best practice when designing a WCF service is to split up your project into seperate assemblies:. Assembly SomeProject.ServiceContract. This assembly contains your service contract (just the interfaces).. Example:.
[ServiceContract (...)] public interface ICan {     [ServiceOperation (...)]    void EatCandies (MyListOfCandies candies);  } 
Assembly SomeProject.DataObjects. This assembly contains all your data objects which is used by your service contract.. Example:.
[DataObject] public class MyListOfCandies : List<Candy> {     ... 

}
In your project, which is consuming your web service reference the assembly "SomeProject.DataObjects" and then add your web service.

You'll see that Visual Studio will no longer generate any stub objects but will use your implementation.. You can do the same with the ServiceContract assembly.

This way you still can use web services, but you will get compile errors when you change your interface..



71 out of 100 based on 81 user ratings 581 reviews