SharePoint Learnings

<SharePoint:AspMenu   ID = "GlobalNav"   Runat = "server"   DataSourceID = "SiteMapDataSource1"   Orientation = "Horizontal"   StaticDisplayLevels = "1"   MaximumDynamicDisplayLevels = "3"   StaticSubMenuIndent = "0"   DynamicHorizontalOffset = "0"   DynamicVerticalOffset = "-8"   StaticEnableDefaultPopOutImage = "false"   DynamicEnableDefaultPopOutImage = "false"   ItemWrap = "false"   CssClass = "topNav" >    <StaticMenuItemStyle   CssClass = "topNavItem"   ItemSpacing = "0" />    <StaticSelectedStyle   CssClass = "topNavSelected"   ItemSpacing = "0" />    <StaticHoverStyle   CssClass = "topNavHover" />    <DynamicMenuStyle   CssClass = "topNavFlyOuts"   />    <DynamicMenuItemStyle   CssClass = "topNavFlyOutsItem"   />    <Dynamic...

http://www.html5rocks.com/en/ http://slides.html5rocks.com/ http://playground.html5rocks.com/

http://chrisstahl.wordpress.com/2010/03/26/breadcrumb-in-sharepoint-design-considerations/

http://chrisstahl.wordpress.com/2011/02/06/validate-a-sharepoint-list-column-with-regular-expression/

http://chrisstahl.wordpress.com/2011/07/18/display-news-pages-with-cqwp-%E2%80%93-part-3/

http://www.n8d.at/blog/sharepoint-2010/round-corners-in-top-navigation-of-sharepoint-2010/ http://chrisstahl.wordpress.com/2011/01/26/customizing-sharepoint-2010-global-navigation-with-css-and-jquery-%E2%80%93-part-iii/

This question has come up a bit so I thought I would make a comment ... "During the time of adding a new webpart, iam seeing .dwp for some webparts and .webpart for some webparts as extension. What is the difference between these two?"  The differance here is that one is a SharePoint webpart and the other is a .NET web part. The .dwp is a SharePoint web part. This would be one like the Content Editor. The .webpart is a .NET framework. The primary differances are that the SharePoint webparts are built with backwards compatibility and more functionality in the web parts communitcation area. If you needed a web part that worked in WSS 2.0 and WSS 3.0, this would be your guy. The later is one that most likely originated in Visual Studio.

I found an interesting article regarding NTLM and kerberos authentication. http://blogs.msdn.com/b/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx

A nice comparisons between asp.net 2.0 custom webpart and sharepoint based web part. ASP.NET 2.0 Web Part SharePoint-based Web Part For most business needs. To distribute your Web Part to sites that run ASP.NET 2.0 or SharePoint sites. When you want to reuse one or more Web Parts created for ASP.NET 2.0 sites on SharePoint sites. To use data or functionality provided by Windows SharePoint Services 3.0. For example, you are creating a a Web Part that works with site or list data. When you want to migrate a set of Web Parts using the SharePoint-based Web Part infrastructure to Windows SharePoint Services 3.0. To create cross page connections. To create connections between Web Parts that are outside of a Web Part zone. To work with client-side connections (Web Part Page Services Component). To use a data-caching infrastructure that allows caching to the content database.

stsadm -o setproperty -propertyname max-template-document-size-propertyvalue 500000000 Good Ref: http://www.law.com/jsp/lawtechnologynews/PubArticleLTN.jsp?id=1202443237483&slreturn=1&hbxlogin=1

At my work we work with a pre-setup development environment, which always includes SharePoint Enterprise edition. But if you have a customer working with the Standard edition, you might be in some trouble during deployment. To prevent trouble, you can downgrade your Enterprise installation by de-activating and de-installing some features. Below follows a small script to remove the Enterprise features from your environment. Replace the http://url with the correct url. There's no other easy way in the GUI. Use stsadm or PowerShell(Disable-SPFeature FeatureFolderName -Url http://url) to disable these features: stsadm -o deactivatefeature -force -url http://url -name PremiumSite stsadm -o deactivatefeature -force -url http://url -name BizAppsSiteTemplates stsadm -o deactivatefeature -force -url http://url -name BizAppsCTypes stsadm -o deactivatefeature -force -url http://url -name IPFSSiteFeatures stsadm -o deactivatefeature -force -url http://url -name BizAppsFields stsadm ...

SharePoint 2010 Interview Questions Administration and General 1.        What are the roles of a SharePoint Administrator? 2.        Why do you think companies go for SharePoint? 3.        What is version history of SP? 4.        What are the various editions of SP 2010? 5.        What do you mean SP Topology? 6.        How do you plan your SP Topology? 7.        What are the pre-requisites to setup a SharePoint Standalone environment? 8.        What are the pre-requisites to setup a multi-server SP farm? 9.        What is the use of Filter Pack? 10.    Can we use SharePoint with a Non SQL Server database? 11.    Can SP run without Active Directory? 12.    What is the diff between NTLM a...