Dave

My feedback

  1. 221 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  2. 190 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  3. 241 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  4. 557 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  5. 6,013 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    193 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  6. 125 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Visual Studio IDE » Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
    Dave supported this idea  · 
  7. 143 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Visual Studio IDE » Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
    Dave commented  · 

    The problem is that call stacks tell you where you're going next, not where you've been. It just-so-happens that in a synchronous world it tells you both. In Rx queries specifically, what we really need is a "query stack" that tells us where we've been, relative to where we currently are. I think that would make debugging async queries much easier. And of course, the same view could be used to simplify debugging Ix queries as well.

    Dave shared this idea  · 
  8. 221 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Visual Studio IDE » IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →
    Dave shared this idea  · 
  9. 1,976 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    47 comments  ·  Visual Studio IDE » Project  ·  Flag idea as inappropriate…  ·  Admin →
    Dave commented  · 

    For me, this applies to having multiple C# projects in the same solution. It's especially slow when each project targets a different platform; e.g., Client Profile, Silverlight 4 and Windows Phone 7.

  10. 2,011 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    59 comments  ·  Visual Studio IDE » UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  11. 839 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Visual Studio IDE » IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →

    Hello again voters and reporters for this UserVoice item

    Visual Studio 2017 RTW, released yesterday, contains fixes to many of the worst issues we are aware of that caused typing delays. To get the benefit, if you haven’t already done so, please download it today from https://www.visualstudio.com/downloads/

    We’ve also included enhanced typing telemetry in the new release, so we can continue to focus on improving those issues that remain, and we’ll alert you via the Visual Studio Performance Center (see https://blogs.msdn.microsoft.com/visualstudio/2016/10/10/faster-visual-studio-15-startup/ for details) when an extension is slowing your typing down.

    We’re not done: we intend to make further improvements to typing responsiveness in updates to Visual Studio 2017.

    Thank you

    Mark Wilson-Thomas and Hemchander Sannidhanam
    Program Manager and Engineering Manager
    Visual Studio Editor Team

Feedback and Knowledge Base