SharePoint Custom code acceptance checklist
The ability to customize sites by adding custom solutions gives Office SharePoint Server 2007 power and flexibility. However, a poorly designed or implemented executable module that runs in a SharePoint farm can do harm even beyond the scope of the Web application for which it was intended. Poorly implemented custom solutions can introduce security or performance risks, increase the cost of support, complicate deployment, and reduce productivity.
You can find more details @: http://technet.microsoft.com/en-us/library/cc707802.aspx
New Microsoft SharePoint 2010 details start to emerge
Following are the New features (rumored) to incorporated into new Sharepoint 2010
- Groove (the offline/online synchronization tool Microsoft bought when it acquired Groove Networks) is being renamed and repositioned with the upcoming release as “SharePoint Workspace Manager.” Update on May 13: Microsoft has confirmed officially the renaming and is saying that SharePoint Workspace Manager and OneNote will be part of the Office 2010 ProPlus SKU. (Microsoft is declining to provide any other information, at this point, on its planned Office 2010 line-up.)
- SharePoint Server 2010 will be 64-bit only and require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2 to run. It also will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
- SharePoint Server 2010 won’t support Internet Explorer 6. From the SharePoint Team blog: SharePoint 2010 will be “targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems. In addition we’re planning on an increased level of compatibility with Firefox 3.x and Safari 3.x on non-Windows Operating Systems,” according to the SharePoint Team Blog.
- SharePoint 2010 will feature a “Web-enabled Ribbon control” and support greater use of Silverlight controls
- CMIS support will allow interoperability between SharePoint 2010 and other content management systems
- The architecture supposedly won’t change as it did between SharePoint Server 2003 to Microsoft Office SharePoint Server 2007, thus insuring less compatibility issues and a smoother upgrade path (at least in theory)
- There’s a new feature, known as “faceted search” coming in the 2010 SharePoint release. No details available yet.
- A new version of FAST Search for SharePoint will be made available at a lower cost. Meanwhile, according to contractor and SharePoint blogger Lars Fastrup (whose blog entry is the source of a lot of this post), “the SharePoint team have scrapped their efforts to make the SharePoint search engine scale beyond 50 million documents in a single index. The argument will be to move to the FAST search engine instead.”
Source: www.zdnet.com
Performance Optimization for WCM Sites & Optimize Sharepoint Site for Search Engines
In internet facing scenario performance optimization is a key thing for the successful implementation of any website. Microsoft has provided good articles related to Performance Optimization for the WCM site in SharePoint & also on how to optimize SharePoint for search engines.
Here is the link:
How to Optimize a SharePoint Server 2007 Web Content Management Site for Performance
http://msdn.microsoft.com/en-us/library/bb727371.aspx
How to Optimize SharePoint Server 2007 Web Content Management Sites for Search Engines
http://msdn.microsoft.com/en-us/library/cc721591.aspx
Site Content And Structure : Find all the pages created using Page layout
In CMS Dependent Report feature is used to identify all the postings which are created using the Template. In Sharepoint Similar feature is available where you can find all the pages which are created using the page layout. This is also useful when you modify the page layout and you want to test all the pages which are created using this page layout.
Here are the steps:
1)Navigate to Site Actions à Manage Content And Structure
2)Go to Master Page Gallery in the folder list
3)Select “Show Related Resources” in the Tool Pane
4)Select the Page Layout for which you want to list all the resources
5)A list of all the related resources for the selected page layout will be listed in the bottom window.
Understand Sharepoint using Dot Net Reflector
Using .NET Reflector, you can browse the classes and methods of an assembly, you can examine the Microsoft intermediate language (MSIL) generated by these classes and methods, and you can decompile the classes and methods and see the equivalent in C# or Visual Basic .NET.
Dot Net Reflector Can be used for the following in SharePoint Scenario, :
- Understand on how SharePoint is doing something, to find what elements can be customized.
- Understand what members to override in classes you create that inherit from SharePoint classes
- .NET Reflector is also an excellent way to know the best practices. Because you get to see how the team at Microsoft actually implemented functionalities. And also you have lots of examples at your fingers tips.
Example Usage of Dot Net Reflector to Under Stand SharePoint Source Code:
· If you want to know on what is happening on load of OOTB Search Results Page then open Microsoft.SharePoint.ApplicationPages.dll and navigate to SearchResultsPage class and click on OnLoad method.
SharePoint DLLS:
- You can find all the SharePoint dlls under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI
- Some SharePoint assemblies(Microsoft.SharePoint.ApplicationPages.dll) are stored in the _app_bin directory of the web application instead of the ISAPI directory in the 12-hive.
Obfuscation:
Sometimes, not too often, when Reflector is disassembling source code for you, it will show “This item is obfuscated and can not be translated” instead of code. This is done for some of the more “sensitive” areas of the code
Downloads:
.Net Reflector: http://www.red-gate.com/products/reflector/
Add-ins: http://www.codeplex.com/reflectoraddins
Note: Review the end user license agreement (EULA) for the relevant Microsoft products before using this tool.
Manage Site Content And Structure in Sharepoint Server 2007
In a Sharepoint the Site Content and Structure page is cool tool for site administrators to manage site content and structure. You can do lot of stuff here in a easy and efficient way
You can do the following
1) Create Sub site/pages/files
2) Delete Sub sites/ pages/ files
3) Move files between libraries
4) Delete Sites/ files
5) Bulk Check in/ Checkout/ Approve pages or documents
6) Publish Pages – If you want to publish the file, you have to check in the file then approve and then publish it You can do this in one step by selecting the Action >> Publish through Site Content and Structure Page.
Navigation Path: Site Actions >> Manage Content And Structure
Securing Publishing Internet Sites – ViewFormPagesLockDown Feature
In Internet facing websites, you don’t want anonymous users to access pages such as AllItems.aspx etc. There is a Sharepoint feature ViewFormPagesLockDown which can be enabled to secure your sites. Find out more details about this feature at: http://technet2.microsoft.com/Office/en-us/library/f507f5d6-4c9d-4f98-909f-069c53b9a3f61033.mspx#section6
Activate Feature:
stsadm -o activatefeature -url <site collection url> -filename ViewFormPagesLockDown\feature.xml
De-Activate Feature:
stsadm -o deactivatefeature -url <site collection url> -filename ViewFormPagesLockDown\feature.xml
Disposing Sharepoint Objects– SPDisposeCheck tool
In sharepoint, you should explicitly dispose SharePoint objects that implement IDisposable when you are finished using them.
The SPDisposeCheck tool will aid in inspecting the disposing of certain Sharepoint objects. This is a must have tool for SharePoint developer to check disposing of SharePoint objects in there custom codes
Download - http://code.msdn.microsoft.com/SPDisposeCheck
Best practices for disposing windows share point objects http://msdn.microsoft.com/en-us/library/aa973248.aspx