Hired Mind

My feedback

  1. 275 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  12 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Hired Mind commented  · 

    Please, I beg of you, just add a StateProvider.LoadStateAsync() method without a type parameter. Even if it only returns the serialized form of the state as a string, that's fine. Right now, actors from 3rd-party libraries are a complete black box at runtime. If something goes wrong, I have no hope of debugging them, because in order to use StateProvider.LoadStateAsync<T>() I have to know the type of their state beforehand. Adding one method could be done quickly rather than create an entire tool set.

  2. 1,070 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Hired Mind commented  · 

    In my opinion this should be done in the service, rather than be baked into Service Fabric itself. There have to be a dozen different ways to do each one of these things. Every feature adds complexity and subtracts reliability.

Feedback and Knowledge Base