Integrating to the max...BizTalk Style

Recently i tried to get a BizTalk 2013 up and running. As i normally do, i use the BTDF to deploy the whole bunch of projects, so i downloaded the betaversion 5.1 from codeplex, and started the deployment. Unfortenately i ran into a problem when trying to deploy to the SSO store. I thought, let’s go crazy and enable SSO, unfortenately, this wasn’t a cakewalk, it wasn’t my birthday, but was certainly treated on some stuff i didn’t request, the pop-up; And of course, the error that helps you out in tough times; C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1684,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk\5.1\Framework\DeployTools\SSOSettingsFileImport.exe" "<…>" /settingsFile:"<…> " /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -532459699. Build FAILE...

Reading application configuration data from a Single Sign-On database is a well-known concept within the BizTalk community. There are other means of retrieving application configuration data for BizTalk, yet retrieving them from SSO is the most powerful one. Microsoft has built an SSO Application Configuration Snap-In that provides a good user experience maintaining custom configuration data. With the Snap-In you will also get code for a .NET Helper Class to support retrieval of application configuration data in BizTalk. This approach has some major benefits. Your application configuration data is cached, has a built in refresh mechanism (ESSO Service) and is secure. What if you have a requirement that to remotely (from a non-BizTalk machine) retrieve application configuration data, because you like to benefit from SSO Config Store? Consider the following diagram In this scenario a mapping is implemented using a Functoid based on a shared helper class that reads the co...