Skip to main content

Hi everyone, I need some independent advice.

A developer was given the task to write a custom service broker for K2 Five. I received a set of DLL files, one main DLL and dozens of other DLLs that are related to the frameworks used. If I were to deploy this to K2 Five, it means copying all those DLLs to "C:\Program Files\K2\ServiceBroker". This creates quite a mess of files there, in that directory, where it's not easy to know what's there "by default" by installing K2 and what's added there because of some custom broker. Isn't there some way to avoid this, e.g. having the main custom broker DLL and other related DLLs in some subdirectory?

Thanks in advance for the opinions.

 

You can create a folder inside the service broker folder where you can keep all your custom files.

You can create a folder inside the service broker folder where you can keep all your custom files.

Could you please be a little more specific? An example?

Hi @Nintex_yousef  would you kindly provide an example? 

We had to deploy the solution as we have, our attempts with DLLs in subdirectories failed, I had to upload all DLLs to the "ServiceBroker" directory. 
If there is anyone who would be willing to share experiences and details, ideally real ones, not some theories on how to solve this, I would be very happy.

 

Just make sure the folder you create has full control rights given to the K2 service account. This is always the way I place custom assemblies in my K2 projects and never faced issues. Take a look at the image above.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings