Sharepoint Migration: Migrate the content to Microsoft Sharepoint

PCVITA Express Migrator for Sharepoint is next generation migration product for Sharepoint Server as part of Sharepoint Migration. It equally fits into Migration 2.0 generation of migration products. The products supports migration of file system content such as Microsoft Word, Microsoft Excel, Microsoft Powerpoint, Adobe Acrobat PDF and various other types of document to Microsoft Sharepoint Server 2007 and Microsoft Sharepoint Server 2010 as part of Sharepoint Migration.

With the high adoption rate of Microsoft Sharepoint Server among enterprises which are small, medium and large in size. It is becoming very difficult for System Administrator to quickly migrate the existing organisation common internal documents related to finance, administartion ,HR, Research and Development and other related documents to quickly migrate them to Microsoft Sharepoint Server.

PCVITA Express Migrator For Sharepoint acts as a smart bridge which is easy to use, effective and efficient to move their existing file system content to Sharepoint as part of Sharepoint Migration.

PCVITA Express Migrator for Sharepoint also supports migrating content which is residing in Exchange Server  Public folder to Sharepoint as part of sharepoint migration strategy. Many organisation are using Public Folder to keep their common document and share across the organisation. These can now be easily migrated to Sharepoint as part of the Sharepoint Migration. This is great in scenario where the Sharepoint Administrator doesn’t need two products to perform the Sharepoint Migration.

PCVITA Express Migrator for Sharepoint comes with the following features

  • Support for adding files and folders.
  • Support for associating meta information with the files.
  • Select the destination document library on target sharepoint server.
  • Create a new document library.
  • Apply filters on the content getting migrated.
  • Report on the migration.

Check more at


WCF: Hosting Service with multiple end points

In continuation of previous post regarding WCF, here goes another. In this post I will do step step explanation for hosting service using config file (remember this is the beauty of WCF, we don’t need to recompile to add multiple endpoints).

The assumtion is readers have already implemented the service contract. I will use a dummy class named IService for my explanation

  1. Create a instance of ServiceHost. 
    1. ServiceHost servicehost = new ServiceHost(typeof(Examples.ServiceImplementation));
  2. Use the Open to start listening.
    1. servicehost.Open();
  3. Now put the following in the App.Config file


Let me explain each of the element

  • The host element declares the base address for the endpoint. In this case its declaring two base address the http address and another one is the tcp address. The host address is used by the ServiceHost to listen on the respective port and address.


  • There are three endpoints


Each endpoint basically is collection of address, contract and binding. Here in the above case the address is not specified as we have already sepcified in the base address. The contract is Examples.IService and the binding is HTTP.

  • The second endpoint


is the TCP endpoint for the same service. Smilar to the previous one this definess the endpoint as collection of Examples.IService as contract and binding as TCP and address is not mentioned and taken from the base address.

  • The last endpoint


is used by the client to generate the meta information about the Service. This  is standard and ideally should be there for each service.I hope the above helps in understanding this beautiful technology.

The author has 10+ years experience with Enterprise Poduct Development. He is also the Co-Founder of PCVITA. He have expertise in Enterprise Architecture, Enterprise Messaging Platform Migration, Email Archiving.

Hello World using Apollo/Adobe AIR

Its been days that I was trying to write a simple app using AIR, the buzz word these days, so downloaded the following

  1. Adobe AIR SDK.
  2. Adobe AIR SDK documentation.

Extract these above stuff after downloading. The documentation is quite good for a HTML /Javascript developer like me. Here I write a Hello World html file using AIR framework.

There are three things to be done

  1. Application XML file.
  2. HTML File.
  3. Executing the application.
Application XML File
  1. Create a XML file named <AppName>-app.xml, here appname can be HelloAIR.
  2. The structure of XML is


The text of rootContent element represents the name of the html file that is associated with the xml.


The following the html code


The appLoad is invoked when the page is loaded. As shown above we are including the standard AIRAliases.js file in the HTML file, so AIR runtime will be initialized. If its initialized the Air.Trace statement is used to print on AIR console “Hello Air”. Then XMLHTTP request is made for getting request.txt file and dumping the content of that file onto the AIR console.

Executing the Application

When the AIR sdk is extracted there are two programs that come

  1. ADL: To execute the AIR application
  2. ADT: to package the AIR application

Use the adl command to execute the AIR application.

The ADL command

When you execute the command with XML as parameter then the following is displayed



As shown above the Hello.AIR is the Air.Trace output and the white console displays thee content of the request.txt file.