Suppose I want to create an API which exposes an OM to the clients. Using my dll, Clients can call in functions like :
CreateRegister() : Creates a list in a particular SharePoint site
AddRecordToRegister() : Creates an item in a specific list(which was created using CreateRegister)
and similarly other methods like DeleteRecord(), DeleteRegister() etc.
Now, Client can use my API with any SP server/site. All they need to do is pass in the SP server site address on which 'Registers/Records' will be created.
I was considering the followign ways to implement/expose my API, but eventually none meet the requirement:
1. One of the ways to talk to SP and do this would be to use SP Client OM inside my API implementation. But for limitations like : I need to provide the same functionality in Silverlight platform and .Net Platform (I will give two sets of dlls, one for silverlight
and one for .Net, and clients can use as per need ) Because of the overhead of writing the code twice as Client OM for Silverlight and .Net are very different requiring different code to be maintained, (Just take the example of ExecuteQueryAsync(), its available
in Silverlight OM and not in .Net OM), this is not feasible for me.
2. This leaves me with an option to create and host a WCF service somewhere so that my clients can consume it regardless of wh
View Complete Post