Difference Between Site Template and Site Definition Before going into direct comparison, let me define both: Site Templates : Are snapshots of sites at a point in time. When a user customizes a site from the UI or SPD, the custom template consists of the difference between the original state of the site (determined by its definition) and the state of the site or list when the custom template is generated. Custom templates remain tied to a particular site definition (for example, the site definition for SharePoint Web sites or Meeting Workspace Web sites), so that if the site definition is not present or is changed, the custom template cannot work. Site Definitions : As the name implies, A Site definition is "core definition of a site”. Each site definition emerges through a combination of files that are placed in the 12 hive of WFE during installation of SharePoint. Site definition files include .xml, .aspx, .ascx, and .master page files, as well as docum...
The story According to Microsoft the CQWP can be used to aggregate content from the following sources: a single list; a site and it’s subsites; an entire site collection; The story demistified The above mentioned is accurate...although not complete. Imagine this real world scenario. Contoso is a medium sized company with approx 25.000 documents. These documents reside in a single Site Collection and are spread over multiple document libraries. Off course we implemented a thorough information architecture and all documents are neatly classified in terms of content type and metadata. Now we have a business requirement: "I want a list of all contracts assigned to me." . Further, an architectural principle states only OOB functionality is allowed. And we are off.... Let's skip a couple of steps to the point, the CQWP is the way to go for this requirement (OOB it is... really... trust me... no you cannot use search because it cannot filter on [me] out o...
very easy understood for basic level....
ReplyDelete