ORIGAM extensibility libraries as NuGet Packages

dev
1

We should externalise extensibility interfaces to a NuGet package so development of new extensions gets easier.

Example:

  • Workflow Service Agents base class
2

I agree. But we should think through the versioning. Are we going to follow the main product versioning, or is it going to be separated. How much is it going to be integrated in our CI/CD?

3

I think this should live in a separate repository and ORIGAM itself should use it as a NuGet package. IMO it should have its own version starting from 1.0.

4

4 posts were split to a new topic: Provide Backend Extensions With More Functions

5

UPDATE: ORIGAM Nuget packages are available here.

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.