Sergio Del Piccolo

The other day I implemented a method that required calling a SharePoint webservice from a K2.Net 2003 solution. K2 created an assembly wrapper for the webservice call. When it came to deploying the solution to our QA environment, my colleague Daniel Gocsman and myself ran into the following compilation error.

“Compile Error: Imports Line 0: Metadata file ‘Installation Path\Workflow\Bin\SiteData.dll’ could not be opened — ‘Version 2.0 is not a compatible version.’

Initially we were concerned about the SharePoint installation being different on the two environments, however we managed to rule that out. The next step was to see which version of the .Net Framework the K2 Server was configured to use. The first place to check was the server configuration in the K2.Net 2003 Service Manager Properties page on the Advanced tab. This correctly displayed the .Net Framework version as 2.0.50727.

After confirming the K2.Net Service Manager was set as expected, we started digging around the configuration files in the K2.Net 2003 installation Bin folder. Looking at the K2Studio.exe.config file we found the .Net Framework version used by the K2 Studio when compiling the workflow solution - it was set to use .Net 1.1. This proved to be the cause of the compilation issue. After updating it to the use .Net Framework 2.0 as the supported runtime version our solution compiled and exported as expected.

Source Code, K2.Net 2003, Workflow

On Monday Source Code released components for their K2.Net 2003 workflow product to integrate to Microsoft Office SharePoint Server 2007 (MOSS). This provides the same functionality that was previously only available with Microsoft SharePoint 2003. This means that K2.net 2003 can:

• Create, update and delete content and any associated metadata
• Access List content
• Access Document Library documents and metadata
• Create workspaces
• Leverage MOSS 2007 event handling allowing for the initiation of workflow process
• Leverage Forms Server 2007 (InfoPath web forms) 

Links: (require you to sign in to the K2.Net portal)

Download Components: K2.Net 2003 MOSS 2007 Components

K2.Net Knowledge Base Article: Leveraging Forms Server 2007 (InfoPath web forms) in the 2003 InfoPath templates

SourceCode, K2.Net 2003, Microsoft, MOSS, Microsoft Office SharePoint Server 2007

I was recently upgrading an existing BizTalk 2004 application to BizTalk 2006 and came across the BizTalk Scheduled Task Adapter. Initially I was fearful that it was going to be an issue during the upgrade, but was pleasantly surprised by the fact that it works in BizTalk 2006 as well as in the earlier 2004 version.

Using the adapter is a simple process requiring the adapter be installed and added to the BizTalk Adapters. New receive locations are then added and configured as Schedule adapters though the BizTalk Administration Console. It allows for scheduling of multiple tasks - in our case, creating messages - on a hourly, daily, weekly or monthly basis. It can be imported and exported using binding files making for a simple deployment.

Microsoft, BizTalk, BizTalk Scheduled Task Adapter