Building a .NET code as an activity and bundle it as local .nuget package

Hello there,

We have a piece of .NET custom code used in the company that I would like to use in one of the automations. I packaged this custom code as a nuget, however i don’t want to publish this package to orchestrator, to prevent other automations from using it. I could use invoke code instead, however this is a large piece of code that would make it hard to debug and would rather leave it as a nuget package so it is easier for me to build, test and debug in Visual studio. Any help or pointers are appreciated.

Thanks.

HI,

Can you elaborate your problem?
I think it’s good to just put the nupkg file at local feed in each production environment. (or put extracted files under nuget global package folder)
If you have any concern, please share it?

Regards,