- Where Developers Learn, Share, & Build Careers
I'm going to start creating a SharePot attribute
cAMl (xml etc) or code object model?
I want to know what is the recommended approach to making lists, columns, content type etc.?
Is there any major danger for any of these methods?
Both required are both useful for a strong solution, neither [full Way] changes to another Needs effectively asks the most spatial data sources, such as lists non-query CAML can be used on the other hand. Directly the Om () program is very useful for updating / updating many things; Including results of various CAML questions! PowerShell CMD allows to expose the OM for easy "inspection" of the current state of the form. Scripts also need to make many things, e.g. Jala- With a little change from the common "template" In addition, there are several actions through OM that are possible with CAM not for example, timer job definitions can not be configured with just the CAML. However, writing a feature receiver to modify SP artifacts can be problematic, especially if the changes should be made later: the modification must also be managed from the receiver - oak! For supported SP creations, always use CAML, unless do not engage things without a good reason. Do not Fight SharePoint Each task is different Use the right (and hopefully "approved") approach to make life easier.
Comments
Post a Comment