First the background story. We develop everything in nugets on the .net side of things. If someone wants to talk to a service you go and download the nuget that offers the require api/stuff to connect to it and done. These applies to all interacting dev teams.
For RO I built some custom nuggets where I embedded the required dlls, plus the generated intf file, some extra client side logic and good to go. This was fine until I wanted clients to call DA methods, not just RO services.
Suddenly it now complaints about licenses. Just to make it even better our nugets are .net standard.
So I read the forum and saw multiple options also saw issues with nugets and licx files etc, etc multiple workarounds but nothing in concrete and I’m failing on something as simple as just deploying a workable client side app.
So, first how do I have a CLIENT app/service/program connecting to a DA server on my case scenario. I dont control other development teams, they just grab their nuget, add connection strings and good to go. I can not ask them to include a separate class and a file with embedded resources, that gets into each team realm and cant get there.
Server side is fine, I control that, client side other teams do it.
I remembered there was a big division on client and server side components just to skip these kind of situations, I’m wondering why do we even need a client side license.
I’m probably just doing things wrong cause I dont see a reason to do it on connecting apps if license is the concern.
Any assistance is extremely welcome, I developed this big thing, relying on DA and now suddenly I cant deploy it for others to use because they are complaining with the license errors. Obviously I ended discovering this up to the moment of integration with other services way to deep into development to find an alternative working solution instead of DA.
Thank you in advance.