Some Development Solutions which I have found

Friday, May 27, 2005

Some Development Solutions

Test

Content Management Server

Visual Studio.NET presents some problems when it is installed on Windows 2003 Server because of the way it stores .tmp files; IIS 6.0 blocks all file types that are not explicitly mapped, and the .tmp file type is not explicitly mapped by default. The workaround for this problem is to either use Visual Studio .NET 2003 when working with Windows 2003 or map the .tmp file extension as a text/plain file type in the MIME type box in IIS.
Installing CMS 2002 with SP1 on a Windows 2003 Server
To install CMS 2002 with SP1 on a Windows 2003 Server, you'll need to perform the installation as we described earlier in this chapter. However, it is important to note that you should not launch the DCA until after you have installed SP1. Therefore, once CMS is installed, do not select the Launch Database Configuration Application check box. Let the installation finish, then install SP1 for CMS, and then run the DCA.
Remember that Windows 2003 installs without IIS, so you'll need to install IIS 6.0 with the components ASP.NET, ASP, and server side includes before you install CMS or SP1.
In Windows 2003, the maximum amount of allowed data upload is configurable in IIS. However, the default number is too low for CMS resources. You'll need to raise this limit to at least 50MB. For information on how to do this, please see the SP1 documentation. XML code will need to be added to the metabase.xml file, and then services will need to be restarted.
The Visual Studio .NET integration is not installed by default. The reason for this is that the component is only necessary on developer boxes. The current version of Visual Studio .NET does not support remote connections for client applications such as the CMS integration. For this reason, the CMS VS.NET integration must be installed on the CMS server. The default install location for the client is C:\Program Files\Microsoft Content Management Server\DevTools.
Setting Up Publishing Tasks
Publishing tasks displayed to authors in the Authoring Connector Wizard are defined in a publishing task list that is set up by a site administrator. The publishing task list is an XML file called PublishingTasks.xml, located on the target server. This enables all clients connecting to the server to view the same list of publishing tasks. In order for a specific task list to be displayed in the Authoring Connector Wizard, the author must have rights to the channel and the template that are specified in the PublishingTask.xml document on the server. The default location of the XML document is :\Program Files\Microsoft Content Management Server\Server\IIS_CMS\OfficeWizard\PublishingTasks.xml.