search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

git rebase and Visual Studio don't get along well #69

Open Tragetaschen opened 9 years ago

Tragetaschen commented 9 years ago

I'm commonly doing git rebase on the command line. Each time I do this, Visual Studio will try to follow all the file changes while the command is running. The error list indicates that the Roslyn services are constantly compiling intermediate code files in various and even non-matching stages as they appear on disk.

In the end, everything settles and runs fine, but there is quite some (unnecessary) load wile git rebase runs and the latter takes much longer compared to when VS is not running.

Please make VS less eager reading changed files from disk.

Tragetaschen commented 9 years ago

Today, VS 2015 RTM hung up during a rebase on the command line. I wasn't able to close the window normally, but it still did respond as far as Windows was concerned. I had to end the process through the task manager…

sayedihashimi commented 8 years ago

TFS:151703 I've added this to our internal TFS, we will reply back here soon.

alexgav commented 8 years ago

@Tragetaschen Hi, would you please provide a simple repro project for this issue that we could take a look at? Is this an ASP.NET 5 project? Thanks!

mlorbetske commented 8 years ago

This is now tracked by TFS#128408

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!