May I kindly ask if there are any plans to make the Service Group feature also available for .NET?
Another reason why I’m asking is that somehow the [ROServiceGroup] attribute seems to be available in the .NET SDK (starting with version 10.0.0.1543 where the feature has been introduced for RO/D) , but obviously doesn’t work.
I don’t want to make any promises, but we’ll try to have a look at implementing it this or next week, as I actually need/could use this for an internal project, myself ;).
Implemented for vNext. For now (and foreseeable future) I’ve kept it simple:
you can optionally attach a single [ServiceGroup] attribute to each service. You can also specify a ServiceGroup on either the ServerChannel or one level up on the NetworkServer (which will propagate it to its channel(s).
If a service has a ServiceGroup set, it will be only callable on channels that have the same ServiceGroup value set. Services without a ServiceGroup will continue to be available on all channels (regardless of whether the channel has a ServiceGroup set or not).
Not implemented yet:
ServiceGroup Codegen for RODL-based servers (though adding the attribute will work)
ServiceGroups don’t yet affect RODL generation, meaning the RODL servers by your channel will include all services, even those that aren’t accessible.