Chris’s SharePoint Reflections

Just another weblog

  • Chris Zhong

    IT consultant Australia

  • Advertisements

Archive for the ‘SharePoint 2010’ Category

Tips for SharePoint 2010 developers

Posted by chrissyz on June 25, 2011

Have you been developing SharePoint 2010 solutions? Here are a couple of tips I would like to share with you.

1. Integrate SPDisposal Checker into your Visual Studio development project

If you have been following my previous blog on disposing SPSite and SPWeb, you should already been familiar with the SPDisposal checker tool. To increase the development efficiency and team collaboration, I normally integrate the output into VS project so I can see the results everytime I build the assembilies. This is very useful on the team project to increase the code quality. The latest version has a Visual Stuido AddIn Option, which integrate the tool into your Visual Studio automatically and output the findings as Error/Warning. Highly recommend!

SPDisposal Checker for Visual Studio

2. SharePoint 2010 Developer Dashbroad

This tool is really good with troubleshooting. It gives us metrics and allows us to trace page load activities. I usually set it ondemand using stsadm command. Of course you can use Powershell as well. I know I am a bit old fashioned. 🙂

After then you should see a nice toggle button on the top right corner of the page. If  not, make sure you have the right permission to the site.


Posted in development, SharePoint 2010 | Tagged: , | Leave a Comment »

SharePoint 2010 Document Management features

Posted by chrissyz on February 17, 2011

Today I would like to talk about a couple of lovely new features in SharePoint 2010 Document Management. Before my ranting starts, I think probably clarify some terminologies first as they can be confusing sometimes (but necessarily have to :)). SharePoint Document management is a subsite Enterprise content management (ECM) workload (remember the classic six wheel?) ECM refers to technologies, methods and tools used to capture, manage, store, preserve and deliver content and documents related to an organization and its processes.

A similar but often confused term is web content management. This technology addresses the content creation, review, approval and publishing processes of web-based content. Key features include creation and authoring of tools or integrations, input and presentation template design and a subset of ECM.

And what about document management?  DM helps organization better manage the creation, revision, approval and consumption of electronic documents. It provides key features such sass document profiling, checking/check out, version control, security etc.

DM is similar to ECM, but the same. Both of them facilitate information life cycle management, encourage collaboration and help manage information. But the key differences are: ECM can manage more than just documents. It brings a large science of record management and manage rich media and even hard copies. DM is purely the management of the documents, with or without any records management

This brings us another term: Record management. Record management is the practice of maintaining the records of an organization from the time they are created up to their eventual disposal. Duties may include classifying, storing, securing and destroying the records.

OK. Now we are all clear. In this post I will cover some DM features that I personally think is very useful. A bit of history, SharePoint 2007 was the first release where SharePoint really broke out of its collaboration role and enabled customers to apply structure and management to their document libraries. A lot of the key DM infrastructure was established in that release: Check in/Check Out, Major/Minor Versioning, Per-Item Permissions, Content Types, Workflows, and the Recycle Bin are just a few examples. In  the SharePoint 2010 version, the team keep up the good work and bring to us some freshness into this space.

  • Document ID

In a heavily used and adopted collaboration environment, one challenge people face is when content is reorganised or moved in the typical course of business. Hyperlinks emailed between team members that point to a document are no longer relevant which causes frustration and loss of efficiency. SharePoint 2010 offers a new capability to assign documents a unique identification number. This unique ID, embedded within a special URL, can then be used to retrieve the document regardless of where it is moved to within the site collection. No more broken links!

  • Document Set    

People often create multiple documents that support a single project or task. SharePoint 2010 includes a feature that enables people to group all of these documents together into a single entity. All documents in a Document Set share the same metadata and the entire Document Set can be versioned as a whole and downloaded as a compressed ZIP file with all contents included. People can also initiate a workflow on the entire Document Set instead of individual workflows for each document.

  • SharePoint Workspace 

Two highlights regarding SharePoint Workspace. The first one is offline capability. Whether you are travelling on an airplane or just have spotty network access, SharePoint workspace allows you to take your content offline. The other one is its rich experience. From drag-and-drop functionality to better performance, SharePoint workspace provides all the benefits to a rich client. And since it is a rich client, it also provides quick and easy navigation among list and libraries. You can simply click from one to another without waiting for webpages to load. The caveat when you are using SharePoint workspaces is you cannot download all content types with it. For example, you cannot download from a calendar, wiki and survey

Posted in General, SharePoint 2010 | Tagged: , | Leave a Comment »