Querying List Items and Using SharePoint Web Services Compared to the Object Model

Question

My company is writing a custom application that needs to do a lot of list item queries across multiple site collections. It will have to work for WSS 3.0, and it would be nice if it worked on WSS 2.0. It will not be designed for MOSS / SPS, but again it would be nice if it worked on these platforms. There are no restrictions on which version of .NET should be used for the solution.

For this type of application, it would be better: object model / API or SharePoint web services? The main factor that I am considering is performance, followed by functions and functionality. Thanks!

Answer 1

The object model is better, since you can access additional functions and complete granularity of list items, such as version history.

The object model is also better for performance (if you properly manage () spsite and spweb objects).

The Sharepoint object model has some differences between 2 and 3, but if you look at the link for v2, it will also work fully with v3.

Web services have not changed at all between v2 and v3, which explains why they do not have new v3 features.

, , , Xml, Xml Xml. .

Answer 2

, , - " sharepoint ?"

• , , -

• sharepoint server, , , API (= ).

Answer 3

+1 .

If you decide to go the OM route, you can compile for both WSS 2.0 and WSS 3.0 from a single source. This should help you get started.

Developing for Sharepoint 2003 using Visual Studio 2008?

How to reference two API versions?

Answer 4

Can OM be used inside an Infopath form? I am currently using web services to pull out the list data that I want, but I would rather use OM.