A new feature added to Skelta Workflow.NET 2004 is Xcopy deployment of dlls. Xcopy enables direct replacement of dlls by ensuring that they are not locked by the processes. Xcopy deployment is not applicable to the Windows Services, Workflow.NET.dll, Workflow.NET.Communication.dll and custom dlls configured for getting connection string.

The steps involved in enabling Xcopy deployment are described here.

1.  Stop all the Skelta Services

2.  Skelta Engine

Make sure that the file watcher has been configured for the application in the Workflow.NET.Config.xml under the application tag. Different directories can be configured using the ";" separator. The "bin" path of the Skelta installation directory and the sub-directories added under the "bin" folder will be considered by default.

3.  Task Scheduler

Make sure that the file watcher has been configured for the task scheduler in the Workflow.NET.Config.xml under the taskscheduler tag. Different directories can be configured using ";" separator. The "bin" path of the Skelta installation directory and the sub-directories added under the "bin" folder will be considered by default.

4.  Web Application

1. Reference the "Workflow.NET.Web.SkeltaXcopy.dll" from "bin" folder of the Skelta installation directory.
2. Make sure that the file watcher has been configured for the application in the Workflow.NET.Config.xml file. (This would have already been done for the engine.)
3. Enable Skelta Xcopy in the Application_Start method in the Global.asax.cs of the application.
   
   
   
   Once Xcopy configuration has been done, the dlls will not be locked by the processes and can be replaced directly.

5.  Start all the Skelta Services

 Skelta - A BPM Workflow Software Company