5 principles for building solutions

In fact, there is one principle. Design your experience and all sorts of best practices that you use when developing ASP.NET web applications for what you do for Sharepoint.

Still, those five points that relate to working with data and about which I wanted to talk.

1. Separate CAML requests from code. Creating a model of its objects. In particular, I would like to draw attention to the fact that if Sharepoint is considered as a repository from the point of view of business logic, then the entire design of the application will be much slimmer. Nobody writes direct SQL requests from .Net code, everyone does the procedures that wrap them in some wrappers and get the output objects. The same can and should be done with CAML requests.

2. Do not try to place all your information in lists, make connections between objects on lists and build complex queries. Especially for large amounts of data.
')
3. Do not be afraid to use Sharepoint only as an interface for displaying and administering if required by the business task.

4. Do not be afraid to use LINQ, AJAX and other latest technologies in conjunction with Sharepoint

5. Reusable use of web parts and use of UserControls. Because it is beneficial for the developer and saves him time and time to develop the project.

PS Let's discuss how you build your applications, how you organize work with data and their display.