The importance of reusable development

When you develop a project you have to take into consideration a lot of things, but one that it is often forgotten is to build components you can later reuse in other projects, there are a lot of reasons for this to happen (short projects, not enough time, specific specifications, etc…).

Well instead of looking at this topic as a cost you should be looking at it as an investment, because the work that you can reuse is definitely going to improve the quality of your next projects, let me elaborate:

  • The already developed components can be applied directly or with few development work.
  • This will gain you project time to either improve your components or to focus on more troublesome areas.
  • By improving your current components or building new ones you will have a broader base to reuse.
  • and so on . . .

What is the cost of building reusable components? Well, you just have to look to the future and try to identify possible aplications of the component, and build them in order to be generic enough to be reusable and specific enough to answer your current project specifications.

Why did i remembered to post on this topic? because I am eating my own doogfood . . . in my current project I am reusing a lot of components that are the result of previous projects, and therefore testing my own theory.

So much more can be said on this subject, that i will probaly will post a part 2 on this topic.

Blogs to take into account :)

I haven’t had much time to post because my main focus has been MOSS 2007 and the projects I have in hands, but today I would like to highlight some of the blogs I usually visit on a daily basis.

Mark Harrison – Sharepoint, CMS and much more

Stefan Gossner – CMS guru and some WSS and MOSS info

João “Jota” Martins – Portuguese Biztalk MVP, and MOSS usefull input

Mário Romano – A coleague and friend new to the blog world, but with very interesting analisys on programming and computers in general.

Joris Poelman (JOPX) – Windows Sharepoint Services MVP, very good MOSS 2007 info

and for last but not least 🙂

Jan Tielens and Patrick Tisseghem both MVP Sharepoint – a must in technological blogs on Sharepoint.

Today I have only referenced non Microsoft people, but next post will be on Microsoft tech blogs 🙂

ECM in MOSS

One of the most exciting developments in MOSS is the integration with ECM (Entreprise Content Management) the ability to provide a solution that builds Intranet / Extranet and Internet access. In the previous versions of the products we needed to have Sharepoint 2003 and MCSM 2002, two separate products with two diferent licensing costs, and the possibility of integration that even though possible it wasn’t always easy.

So now we have the ECM in MOSS but most of the info we have access are overviews on enhancements, key features and advantages, and there are very few end to end descriptions on how to build and deploy a new ECM solution. I have found a few examples and some info:

This is a subject that i am very interested, i will be posting again on this specific subject soon.

Migrating MCMS database to MOSS 2007

Stefan Gossner has written an article on setting up the MCMS to migrate to MOSS 2007 and another about problems in migration MCMS database to MOSS 2007, more specificaly about the Noexisting User. Besides the importance of the the articles itself (migration between CMS and MOSS) we also have some info about the diferences between the latest builds and Beta 2.

“A couple of users asked me how I setup my system to do the migration of a MCMS database to MOSS 2007. . . .”

“Today I had to upgrade my MOSS installation to the latest builds as I ran into blocking bug in Beta 2 which prevented me from being able to continue with my MCMS migration.

After upgrading I did another analysis step to see if something changed.

Indeed there were a couple of changes:

The Host header mapping enabled warning, the deleted items and the nonexistent user warning no longer showed up – might mean that this is now automatically handled by the new build. Not sure what this means for the deleted items and for the users. Will these now be migrated or ignored? We will see…”

You can find this article here.

SharePoint Server 2007 for MCMS 2002 Developers

From Microsoft, this is probably one of the most important articles on Sharepoint 2007 and CMS 2002, it simply explains what has changed and how things are done now. Very usefull specially to CMS 2002 developers. This post has been corrected to enable the full article to remain in the original place, and I will just highlight some parts.

Office SharePoint Server 2007 default functionality frees you from the routine work of creating custom code for common tasks, and in addition, offers the following new features:

  • Extensible workflow
  • Enterprise Search engine
  • Multilingual site publishing
  • Recycle bin (new for SharePoint Server)
  • RSS feeds
  • Single Sign On


You no longer have to deploy a solution based on Microsoft Office SharePoint Portal Server 2003 and a solution based on MCMS because, in SharePoint Server, you can develop a single solution that includes both content management and collaboration capability. SharePoint Server is built upon Microsoft Windows SharePoint Services (version 3), and offers a powerful new API. You have access to built-in Web Parts, lists, document libraries, templates, workflows, and RSS.

some of the most important topics :

  • Page Processing
  • Channel vs Sites
  • Template Objects vs. Siet Content Types
  • Master Page and Page Layout Gallery
  • Placeholder Definitions vs Site Columns
  • Template Files vs. Page Layouts
  • Placeholder Controls vs. Field Controls
  • Postings vs. Pages
  • Resource Galleries vs. Image and Document Libraries
  • Roles vs. Permission Levels
  • Right Groups vs. User Groups
  • Publishing Events vs. Windows Workflow Foundation
  • Visual Studio 2003 vs. SharePoint Designer 2007
  • Site Deployment Code vs. Administration Tasks
  • Navigation
  • Authentication
  • API Changes

I know it is pratically the all article I’m highlighting, but that is because it is really an important article.

You can find this article here.

SharePoint and CMS migration to MOSS 2007

This is a super post about Sharepoint and CMS migration to MOSS 2007, I have made reference to 3 contributers: Arpan Shah, Andrew Connel and Stefan Gossner.

From Arpan Shah's blog:

CMS Migration

Over the last one year, I've been "talking" a lot about the great things that are coming out in Office SharePoint Server if you are a CMS customer. Yesterday, we released some great guidance and tools on helping CMS customers move from CMS to Office SharePoint Server 2007.

 You can find this article here.

From Andrew Connel:

MSDN now has a “SharePoint Server Migration Center” site: http://msdn.microsoft.com/office/server/moss/2007/migration/

SharePoint Portal Server 2003 and Content Management Server 2002 are truly integrated into a common architecture in Microsoft Office SharePoint Server 2007. Many tasks such as navigation, summary links, and scheduled deployments can now be performed by users or IT professionals. SharePoint Server 2007 is built upon Microsoft Windows SharePoint Services (version 3), which is based upon Microsoft ASP.NET 2.0. As a result, you can also use functionality such as master pages, authentication providers, and navigation providers in SharePoint Server. 

You’ll not only find SharePoint specific upgrade & migration content, but you’ll also find MCMS related upgrade & migration content, including (all new content except for the second one, which was updated from it’s original NOV-2005 release):

The first and third links in the list above are great reads for MCMS developers who are looking at upgrading to WCM in MOSS 2007.

Check out the resources here http://msdn.microsoft.com/office/server/moss/2007/migration/ under the Content Management Server section! It includes 4 whitepapers and a CMS assessment tool. Make sure you read the Assessing and Analyzing Your MCMS 2002 Application for Migration whitepaper before you use the tool!

The Microsoft CMS Assessment tool is an application that collects data for a site created with Microsoft Content Management Server (MCMS) 2002. Use the CMS Assessment Tool to assess your MCMS 2002 site to determine the level of work required to migrate the site to Microsoft Office SharePoint Server 2007.

» MCMS 2002: CMS Assessment Tool

You can find these articles here and here.

From  Stefan Gossner

Together with the beta 2 of MOSS 2007 and WSS 3.0 Microsoft released a couple of nice documents and tools which should help MCMS customers to plan and prepare the migration to the new version on the SharePoint Server Migration Center

Articles and Tools

Webcasts

Read more on the SharePoint Server Migration Center

You can find this article here.

Content Management Server 2002 Developer Portal

From MCMS faq.com:

Content Management Server 2002 Developer Portal

MCMS 2002 and SharePoint Portal Server 2003 are truly integrated into a common architecture in Microsoft Office SharePoint Server 2007. In SharePoint Server 2007, many tasks such as navigation, summary links, and scheduled deployment that an MCMS 2002 developer would perform can now be performed by users or IT professionals.SharePoint Server 2007 is built upon Microsoft Windows SharePoint Services (version 3), which includes many features previously provided by MCMS 2002, such as workflow and authentication. In addition, because SharePoint Server 2007 is based upon Windows SharePoint Services V3, which is based upon Microsoft ASP.NET 2.0, you can use functionality such as master pages, authentication providers, and navigation providers in SharePoint Server 2007.

You can find this article here.

Create a free website or blog at WordPress.com.

Up ↑