sayedihashimi
commented
8 years ago TFS Bug#231170
Open scottaddie opened 8 years ago
sayedihashimi
commented
8 years ago TFS Bug#231170
webtools-bot
commented
7 years ago The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.
If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.
By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.
Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!
Assume that I'm working in a project in which a Grunt task has been bound to the AfterBuild event:
Upon building the project, focus is set to the Output window to display progress. This works just as I'd expect it to. Why isn't focus set to the Task Runner Explorer window at some point during that build? For long-running Grunt or Gulp tasks, the user will probably manually open Task Runner Explorer to see what's going on. Why not save the user a click and automatically set focus? We're curious people and want to know what's going on at all times.
I envision focus being set to Task Runner Explorer when the blue status bar indicates that the task is running. When the task has completed, focus should return to the Output window to indicate completion of the entire build process.
Here's how things currently work in VS 2015 Update 1 with a single Grunt task bound to AfterBuild: