I've stumped K2 support with this one, but I'm hoping someone in the community has more experience with this.
I'm trying to automate deployments of workflows and SmartObjects using msbuild (see here). I can create a deployment package from within Visual Studio, but I need to be able to automate that process as well (similar to here).
I am able to build my process using msbuild, but when I try to create the deployment package using the K2 API, the APi throws an exception:
The'CodeExtender' extender project output assembly is missing. Ensure that the project has been built.
I get this message unless the process is built from within Vistual Studio. If I build within Visual Studio, the deployment package is created just fine with the exact same code.
So my question is: has anyone successfully created a deployment package without first building in Visual Studio? Any pointers on the secret sauce VS is adding to the build process that makes the deployment package process work?