It is not exactly a bug, but rather irritating "feature" of Paket extension for VS: when it is configured to restore missing packages before each VS build it creates separate pane "Paket" in the Output window and switches to it every time build starts, mostly two write one line that all packages are up to date.
When the build starts most look at the Output window to see the Build pane, not Paket pane.
This design can be improved in a number of different ways, but the easiest one in my opinion - don't create separate Output pane for Paket - let it write what it has to say right to the normal Build pane!
If for some reason separate pane MUST be created, then don't let it steal focus from the Build pane, at least not in the case when it does not have much to say.
It is not exactly a bug, but rather irritating "feature" of Paket extension for VS: when it is configured to restore missing packages before each VS build it creates separate pane "Paket" in the Output window and switches to it every time build starts, mostly two write one line that all packages are up to date.
When the build starts most look at the Output window to see the Build pane, not Paket pane.
This design can be improved in a number of different ways, but the easiest one in my opinion - don't create separate Output pane for Paket - let it write what it has to say right to the normal Build pane!
If for some reason separate pane MUST be created, then don't let it steal focus from the Build pane, at least not in the case when it does not have much to say.
Does it sound reasonable?
Thank you! Konstantin