The latest build of this product (v22.1.4) was released 2 months ago, which was before this thread was created.
Posted 20 days ago by Tobias Lingemann - Software Devolpment Engineer, Vector Informatik GmbH
Avatar

Hi,

we use different parts of your components across multiple projects, that often share a common project structure or output directory. This means when we want to update a single component, like the .net add-on, we need to update all your components in all our projects. Even if the other projects don't use the add-on at all. Simply because all use the same shared component, which must be updated for the add-on.

This makes things more complicated on our behalf. Is there a way, we could update the .net add-on separately, without updating everything else?

I have tried to create a custom nuGet package, that works with other builds of the same major version (22.1), but that didn't work out.


Best regards, Tobias Lingemann.

Comments (1)

Posted 20 days ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Tobias,

All of are assemblies are developed with the expectation that common Types in shared components are all from the same version when they are loaded. Unfortunately, we wouldn't be able to support a scenario where add-ons are versioned separately since they often rely on those common Types.


Actipro Software Support

Add Comment

Please log in to a validated account to post comments.