Sunday, March 24, 2013
Thursday, May 3, 2012
Thursday, March 4, 2010
I have got the wonderful chance to meet Joel and Shahid Gaglani (once again). Joel as always done sessions with smiles and Shahid was not lined up for the session (unfortunately).
The other exciting figures of the event are Scott Hanselman and Micheal Noel!. Scott is excellent in his work, his session was awesome!...You are the man!.. You made the Asp.net MVC simpler to me.
Noel, you are the ocean of knowledge. You have the stuff to speak!
The very interested tracks were on MVC and SharePoint!
Saturday, August 15, 2009
There are two kinds storage containers inside SharePoint: 1) Administration Store ‐ This store contains data relatedto site administration, containing information such as server farm and node setup, etc. ; and 2) Content Store ‐ Thisstore contains data related to site hierarchy as well as the content associated with the site, including user data ,layout, menu items, etc. The content database is where most application data will tend to reside. The use ofSharePoint storage containers is centered on the notion of list. A list is a collection of items or rows and can be usedto store application data.
While creating an instance, the SP admin will choose a template that are registered in the server farm, (site definitions). In case, the site need to be modified after it has been provisioned,
Features allows change to an existing functionality associated with a provisioned site. Like SiteDefinition, Features is a collection of XML files that, once registered, becomes available to site administrators. A Feature applied at a SPSite scope is automaticallyavailable to all nested SPWebs
navigation, contents, custom code etc. Once the template or site definition has been defined and registered, SharePoint administrators can use them to provision sites.
There are two major motivations for choosing MOSS/SharePoint as an application development platform:
- The need to provision more than one website based on a logical grouping ‐ such as department, regionor country ‐ rather than have one website that serves all users.
For example, a company needs to develop a web application for its partners that allow them access to pertinent sales information. The partners may want the sales information to surface differently (i.e. grouped byregions vs. grouped by cities), or they may want to co‐locate additional applications on the same page(i.e. a tax calculator). Rather than building all of this personalization in code, it is easier to provision asite for each partner that is based on a single common site blueprint. Each partner can then customizetheir site based on their specific needs via a single code base.
- The need to manage un‐structured content (i.e. documents, web casts, etc.) along with the structureddata stored in a SQL database. A distinction between the structured content and unstructured content is that the former deals with data that can be viewed andmanaged using set‐based groupings (database views), whereas, the latter deals with data that ismanaged as explicit standalone entities along with the associated metadata. Not only is it important tomanage the integrity and security of standalone entities (such as documents); it is also important tomanage the relationships among them (for instance, the association relationship between a documentand structured application data).
Microsoft has introduced platforms/products such WSS and MOSS that build on ASP.NET technology to provide higher‐level building blocks such as the document library and lists, end‐user‐definedforms, search, personalization and workflow.