Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Site column, content type, list definitions - CAML versus Object

  Asked By: Prince    Date: Dec 08    Category: Sharepoint    Views: 1821

I'm reading this invaluable resource called "Inside Windows SharePoint
Services 3.0" authored by Ted Pattison and Daniel Larson and I'm looking at
Chapter 6 - Lists and Content Types. It shows examples of creating definitions
for and provisioning site columns, content types, and lists using both CAML and
the object model. In the chapter summary the author states "Although there is
extra work involved with using CAML to create features containing custom
definitions for site columns, content types, and list templates, it is often
well worth the effort required. CAML provides the most reliable approach for
creating storage mechanisms that can be reused across sites, farms, and various
business solutions."

I guess I'm wondering if anyone can verify this statement and explain why CAML
is better? I've just (finally) gotten my first list definition/instance
installed via a feature using CAML and I can't tell you the number of hours it
took me (I lost count after 10). It's nearly impossible to troubleshoot when
something goes wrong. I spent at least 8 of those 10 hours using trial and
error with the various CAML attributes and searching aimlessly through the
diagnostic logs. Not to mention the WSS SDK is very inaccurate. The object
model seems much more straight forward, however, I'm hesitant to use it based on
the author's statement above. I'm hoping some of you more experienced
developers can shed some light on best practices for defining and provisioning
site components, even if it's a link to a blog.



No Answers Found. Be the First, To Post Answer.