Share Point

Bu makalenin Türkçe versiyonu için tıklayınız...

The most annoying thing about development of Microsoft Office SharePoint Server 2007 ( MOSS 2007 ) is, there is no default support for development on client operating systems like Windows XP or Windows Vista.

Microsoft has released 2 extensions on Visual Studio 2005 for Windows SharePoint Services 3.0 ( WSS 3.0 ) and MOSS 2007. These can be downloaded on the sites linked below:

http://www.microsoft.com/downloads/details.aspx?familyid=19f21e5e-b715-4f0c-b959-8c6dcbdc1057&displaylang=en ( Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions )

http://www.microsoft.com/downloads/details.aspx?familyid=6d94e307-67d9-41ac-b2d6-0074d6286fa9&displaylang=en ( SharePoint Server 2007 SDK: Software Development Kit and Enterprise Content Management Starter Kit )

The extension for WSS 3.0 must be installed on a server which WSS 3.0 s installed. When it comes to WSS 3.0, it can be installed only on server operating systems like Windows Server 2003 and later. So, WSS 3.0 extensions can not be installed on client operating system. ( This extension is avaliable for only 32 bit server operating systems and 64 bit version of this extension is not avaliable. ). In the extension for MOSS 2007, there are project templates for developing MOSS 2007 workflows, but if you install this extension is installed on a client operating system, when you create a MOSS 2007 workflow project, you get missing DLL errors. In this article, we will talk about copying the needed DLL's for developing MOSS 2007 projects to a client operating system.

First of all, the operation I am going to define in this article may create a legal problem since the operation includes copying the needed DLL's to a client operating system.

MOSS 2007 DLL's are located at the Global Assembly Cache ( GAC ). To get the list of this DLL's, you need to navigate to the C:\Windows\assembly folder. If you do not use the command prompt and use Windows Explorer to reach the C:\Windows\assembly folder instead, you get the nice list look of the GAC instead of a real folder listing of that folder. That's why you have to use the command prompt to reach the GAC folder. On the command promt, navigate to the C:\WINDOWS\assembly folder and run the "dir" command. With this operation you'll get the list of the folders as below:

• GAC
• GAC_32
• GAC_MSIL
• NativeImages1_v1.1.4322
• NativeImages_v2.0.50727_32
• temp
• tmp

If you enter the GAC_MSIL folder and type "dir" command, you'll get the list of the DLL's on GAC as folders. You have to copy the DLL's listed below from GAC folders and C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI install location to another folder on the server:

• Microsoft.Internal.Mime.dll
• Microsoft.Office.DocumentManagement.DocSite.dll
• Microsoft.Office.Excel.Server.CalculationServer.dll
• Microsoft.Office.Excel.Server.CalculationServer.Proxy.dll
• Microsoft.Office.Excel.Server.dll
• Microsoft.Office.Excel.Server.resources.dll
• Microsoft.Office.Excel.Server.Udf.dll
• Microsoft.Office.Excel.Server.WebServices.dll
• Microsoft.Office.Excel.WebUI.dll
• Microsoft.Office.InfoPath.dll
• Microsoft.Office.InfoPath.Server.Administration.CommandLine.dll
• Microsoft.Office.InfoPath.Server.dll
• Microsoft.Office.InfoPath.Server.Intl.dll
• Microsoft.Office.InfoPath.Server.Intl.resources.dll
• Microsoft.Office.InfoPath.Server.Pages.dll
• Microsoft.Office.Policy.Barcode.Generator.dll
• Microsoft.Office.Policy.dll
• Microsoft.Office.Policy.Intl.dll
• Microsoft.Office.Server.Conversions.dll
• Microsoft.Office.Server.Diagnostics.dll
• Microsoft.Office.Server.dll
• microsoft.Office.Server.intl.dll
• Microsoft.Office.Server.Search.dll
• microsoft.office.server.search.intl.dll
• microsoft.office.server.search.intl.resources.dll
• Microsoft.Office.Server.UI.dll
• Microsoft.Office.SlideLibrary.dll
• Microsoft.Office.Workflow.Feature.dll
• microsoft.office.workflow.routing.dll
• microsoft.office.workflow.routing.intl.dll
• microsoft.office.workflow.tasks.dll
• Microsoft.SharePoint.AdministrationOperation.dll
• Microsoft.SharePoint.Diagnostics.dll
• Microsoft.SharePoint.dll
• Microsoft.SharePoint.Dsp.dll
• Microsoft.SharePoint.Dsp.OleDb.dll
• Microsoft.SharePoint.Dsp.SoapPT.dll
• Microsoft.SharePoint.Dsp.Sts.dll
• Microsoft.SharePoint.Dsp.XmlUrl.dll
• Microsoft.SharePoint.intl.dll
• Microsoft.SharePoint.Library.dll
• microsoft.sharepoint.portal.dll
• microsoft.sharepoint.portal.intl.dll
• Microsoft.SharePoint.Portal.SingleSignon.dll
• Microsoft.SharePoint.Portal.SingleSignon.Security.dll
• Microsoft.SharePoint.Portal.Upgrade.dll
• Microsoft.SharePoint.Publishing.dll
• Microsoft.SharePoint.Publishing.Intl.dll
• Microsoft.SharePoint.Publishing.Intl.Resources.dll
• Microsoft.SharePoint.Search.dll
• microsoft.sharepoint.search.intl.dll
• microsoft.sharepoint.search.intl.resources.dll
• Microsoft.SharePoint.Security.dll
• Microsoft.SharePoint.SetupConfiguration.Intl.dll
• microsoft.sharepoint.WorkflowActions.dll
• microsoft.sharepoint.WorkflowActions.intl.dll
• microsoft.SharePoint.workflowactions.intl.resources.dll
• microsoft.SharePoint.workflows.dll
• microsoft.SharePoint.workflows.intl.dll
• microsoft.SharePoint.workflows.intl.resources.dll
• Microsoft.Web.Design.Server.dll
• Microsoft.Web.Design.Server.intl.dll
• OWSSVR.DLL
• SHTML.DLL
• SSOCLI.DLL

After the copy operation, copy all the DLL's to the client machine and install all of the DLL's to GAC. OWSSVR.DLL, SHTML.DLL, SSOCLI.DLL DLL's may create an error whlie installing to GAC, but that does not create a problem. The error occurs beacuse these dll's are not managed. After this operation your client operating system is ready for developing on MOSS 2007.

Author: Nezih Tınas ( MVP )

E-Mail: nezih.tinas@paylasimnoktasi.com

Article Date: 23.06.2007