Nathan

My feedback

  1. 140 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Nathan supported this idea  · 
  2. 1,066 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  17 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Nathan supported this idea  · 
  3. 370 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Nathan supported this idea  · 
  4. 996 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nathan commented  · 

    We just had a deployment last night, where a common application was getting patched, and we needed to shut down a dependent application while it was happening. Since there is no way to just "shutdown" the app, we had to remove it as well. After the patching was done, we reinstalled the wrong dependent app, and it took 2 hours to figure out what happened. If we had been able to just shut down the app without uninstalling, there wouldn't have been an issue.

    Nathan supported this idea  · 

Feedback and Knowledge Base