Mike Krüger

First I implemented another solution but I think I solved the old bug. However with a small delay but I think it's acceptable.

@sevoku the nuget scenario is a problem on "rename" as well - it's not specific to that one and in no way a problem here IMO. The git update was...

"but it can break easily since anything at any time" The same argument applies for: Add Solution folder Rename This is not specific to that change in any way. However...

Found an easy fix : just the node that's edited can't be updated - update on other nodes work. If the node that's edited is updated the update is canceled....

/fixed the activeDocument assignment - that was wrong. Y there are different scenarios where that can happen.

How about that ? Just giving cutting the GetContent pipe on disposed Documents ?

No idea what you mean with remove active document from the list. At that point it's no longer an IDE document at that point it's a roslyn document. And does...

In general I don't think that this change is harmful. Even if there is a deeper problem it makes the code more solid.

@monojenkins backport release-8.3 @monojenkins backport release-8.4

This surely doesn't fix the cause. Something from code analysis is calling the document after it's been disposed.