Using the SharePoint 2010 Client Object Model - Part 6

re: Using the SharePoint 2010 Client Object Model - Part 6

Alex — Wed, 08 Aug 2012 00:47:51 GMT

Hi Steve,

Great article. But I was wondering if there is any way to access custom properties of a webpart. The webpart is not bound to any underlying list item and the content are inline custom properties. Is it possible to access the values of those properties using COM?

re: Using the SharePoint 2010 Client Object Model - Part 6

Jonathan — Wed, 22 Sep 2010 10:19:10 GMT

Great series of articles. Would you consider doing one about Surveys? Getting a list of survey questions, submitting a survey, finding out if the survey allows multiple responses, if the current user has already submitted a response, etc.

re: Using the SharePoint 2010 Client Object Model - Part 6

Jack Harris — Thu, 26 Aug 2010 23:08:03 GMT

Microsoft finally got around to fixing a design flaw. Sharepoint is nothing more than a meta-database plan and simple. All the application development effort inside the Sharepoint environment was MADNESS from the start.

ASP.NET is a great application and WCF is great for offering services. These interfaces where always there as web services and it just took some imagination to place an object model over it. I would never do development inside of Sharepoint unless is was an admin tool.

Microsoft finally caught up to proper design after all this time and angst. But are the going to release the Client Object Model code so that you can port it to interface from disparate client? My guess is no. Which means I'll have to still use the raw Web Services and construct my own client object model.

There are many more clients these days that are running on OS's other than Windows.