.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!



Home >> Articles >> SharePoint >> Post New Resource Bookmark and Share

 Subscribe to Articles

Seven quick points in Understanding SharePoint 2007 list definition

Posted By :Dhananjay Kumar      Posted Date :08/03/2010   Points :25   Category: SharePoint    URL: http://www.dhananjaykumar.net

Seven quick points in Understanding SharePoint 2007 list definition. This article will give basic 7 theatrical points on SharePoint List definition.
 


Objective


This article will give basic 7 theatrical points on SharePoint List definition.

  1. When we create a new site in SharePoint, it gets created as instance of SharePoint Site Definition. Each instance of Site Definition is having List Definitions. So when we create a list in SharePoint site, it gets created as instance of List Definition of the site. 
  2. Each list gets its definition from the two files. These files are applied globally to the site.

    Two files are as below,

  3. Each List folder is having 5 files. They are as follows

    These files can be found at 
    Local_Drive:\Program Files\Common Files\Microsoft Shred\web server extensions\60\TEMPLATE\Locale_ID\Site_Definition\LISTS
    directory

  4. All the three XML files for a list use CAML language to define how list instance should be created.
  5. Never modify content of FLDTYPES.XML.
    Because wrong updating or modification in this file can break the entire site definition for particular front end server.
  6. All ASPX page of a list item contains same Page Directive, Meta Data, Script, and Server controls.
  7. Each ASPX page contains a table with three rows.
TOP Navigation
Title
Left Navigation Content

 
In next articles; I will show how to customize above four parts of a SharePoint List form. Thanks for reading.


Featured Articles


Best Practices No 5: - Detecting .NET application memory leaks
Memory leaks in .NET application have always being programmer's nightmare. Memory leaks are biggest problems when it comes to production servers. Productions servers normally need to run with least down time. Memory leaks grow slowly and after sometime they bring down the server by consuming huge chunks of memory. Maximum time people reboot the system, make it work temporarily and send a sorry note to the customer for the downtime. ... Read More
.NET Best Practice No: 1:- Detecting High Memory consuming functions in .NET code
One of the important factors for performance degradation in .NET code is memory consumption. Many developers just concentrate on execution time to determine performance bottle necks in a .NET application. Only measuring execution time does not clearly give idea of where the performance issue resides. Ok, said and done one of the biggest task is to understand which function, assembly or class has consumed how much memory. In this tutorial we will see how we can find which functions consume how much memory. This article discusses the best practices involved using CLR profiler for studying memory allocation.... Read More
How to improve your LINQ query performance by 5 X times ?
LINQ has been criticized by many early adopters for its performance issues. Well if you are just going to drag and drop using DBML code generator I am sure you will land up in to mess. Try doing this make a simple LINQ to SQL project using DBML and see your SQL profiler, I am sure you will never like to touch DBML code generator again. ... Read More
Responses

No response found. Be the first to respond this post

Post Comment
You must Sign In To post reply
Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend