How can we improve Microsoft Azure Service Fabric?

Move IService and related remoting interfaces to their own namespace

Please move IService and the related remoting interfaces into their own package/namespace so that you can reference just those and not be coupled to the entire set of service fabric libraries

It is disappointing that in order to use remoting any service must ultimately inherit from IService. This means you are then coupled to not only the IService interface but ultimately the entire Service Fabric set of namespaces as IService resides in Microsoft.ServiceFabric.Services.Remoting, which of course is dependent on the other packages as well.

As discussed here

113 votes
Sign in
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Denis Pitcher shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Microsoft
Signed in as (Sign out)
  • Wei Peng commented  ·   ·  Flag as inappropriate

    In 2019, the existing of this issue (still) makes me really disappointed.

  • Martin commented  ·   ·  Flag as inappropriate

    Yeah, this is horrible, horrible mistake. The Service Fabric is just only way how I'd like to run my application. With this unfortunate coupling I can forget to do easy .NET Core Web API based on same interface for instance.

  • Patrick commented  ·   ·  Flag as inappropriate

    I do agree. I am always leary when I need 1 package and it brings in several more.
    Especially when all I need is a literal do nothing interface.

Feedback and Knowledge Base