Anders

My feedback

  1. 20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Visual Studio IDE » IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →
    Anders supported this idea  · 
  2. 2,352 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    257 comments  ·  Visual Studio IDE » Languages - Visual Basic  ·  Flag idea as inappropriate…  ·  Admin →
    Anders supported this idea  · 
  3. 550 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    55 comments  ·  Visual Studio IDE » IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →

    Hello,

    We’ve begun work on this and are considering changing the default location for new projects to C:\\USERPROFILE\Source\repos. Would this be a reasonable change to address the problem of “clutter” in the Documents folder? This is currently the default for cloned repositories, so all projects would be in a singular default location.

    As well, you still retain the option to change the default if you’d like.

    Allison Buchholtz-Au
    Program Manager – VS IDE

    Anders supported this idea  · 
    Anders commented  · 

    Also the IISExpres, SQL Management Studio, Visual Studio and OneNote folders should go away.

    Why do I automatically get all these empty placeholder folders? Does noone at Microsoft enjoy a clean structure themselves?

    The IISExpress casues a nightmare with technologies like OneDrive and windows built in profile/folder sync. The IISExpress folder is actually more of a temp folder with all its continous logging etc.

    Now if Microsoft stops forcing a structure into my data folder, other vendors might also stop creating folders for me there. After all, the documents folder should be mine to control the structure of.

  4. 94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Visual Studio IDE » UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →

    Rest assured, we’re not deliberately ignoring the bug. Far from it, in fact. The issues with XDesProc are tricky, as I’m sure you’d understand. While the reliability is getting better and we’re seeing a decrease in reported issues, we’re still making some large steps to improve it further. Naturally, if you’ve got any details on what you were doing when XDesProc caused issues, we’d love to hear them and make sure that our efforts address the issues. You can report these issues using the “Report a problem” feature on the Help menu in Visual Studio, and also make sure that you’ve configured Visual Studio to send us crash reports (On the Help menu, select Settings under Send Feedback)

    In the meantime, I can lay your fears to rest and assure you that we’ve redoubled our efforts to make the XAML designer the best designer anywhere.

    -Dante Gagne
    Visual Studio Program…

    Anders supported this idea  · 

Feedback and Knowledge Base