Jamie Clayton

My feedback

  1. 1,648 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    56 comments  ·  Visual Studio IDE » IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →

    This is a great idea! We completely understand how auto-switching SCC providers would help increase your productivity. Although we plan to make this available to you in the near future, we are still in the planning process and may reach out for your feedback as we start to define how tackle this problem. We will check back as soon as possible with any updates to this request. Allison Buchholtz-Au: VS Program Manager ​​

    Jamie Clayton commented  · 

    I believe I run HG, TFS, and the occasional SVN every week as a consultant with multiple customers and projects I'm involved with.

    Jamie Clayton supported this idea  · 
  2. 2,939 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Visual Studio IDE » UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
    Jamie Clayton supported this idea  · 
    Jamie Clayton commented  · 

    It would also be ok if the XAML design errors could be displayed prior to running the application. E.g. StaticResource references that don't exist, Source paths that are relative, making it a pain to move files around. All these currently cost time to re-test and find rather than let the IDE warn you of the issue prior to build and debug.

Feedback and Knowledge Base