Extensions: generate definitions and implementation into seperate projects

By Gert-Jan Vernooij on 9 Nov 2017

When creating an extension with Integration Studio all generated files are put in one assembly (in Visual Studio all in one project).
I think it is a common good practice to put definitions and interfaces in an assembly seperate from the implementation. 

I have a scenario that is impossible to implement now. I need to support different versions of an implementation of the extension simultaneously and need to switch between these versions run-time.
Furthermore I want to separate these versions in different Visual Studio projects. But I run into circular dependencies. The project generated by Integration Studio needs references to the projects with the implementations and these projects need a reference to the projects containing the interface and types generated by Integration Studio.

If the Interface, Structures, Entities and Reocrds would be generated into a seperate assembly as the implementation of the interface I would have no problem using them in all projects.


erik berg9 Nov 2017

This option should also be in Service Studio as well base around the a single solution per Four Layer Canvas.  The Solution will define the layers as a ayer solutions where each layer solution contains one or more projects geared at domain something at that layer.

Justin James11 Nov 2017

"I need to support different versions of an implementation of the extension simultaneously and need to switch between these versions run-time."

This sounds *horrific*.

J.Ja