anonymous

My feedback

  1. 70 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    anonymous supported this idea  · 
  2. 246 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    anonymous supported this idea  · 
  3. 937 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    66 comments  ·  Visual Studio IDE » Install  ·  Flag idea as inappropriate…  ·  Admin →

    We expect to make significant progress on this front in the upcoming release. There are some components which must be installed to the system drive for various reasons – for example, Windows hotfixes and .NET Framework releases. But we think we will be able to do a better job of honoring the chosen location in the next release.

    To give some transparency into the design process, one interesting wrinkle to this problem is third-party components that we install. If you choose to install Visual Studio to (say) D:\VS, where should we install something like Git for Windows or the Android SDK (if you select those components)? Should we install them into a subdirectory of D:\VS, even though other apps may use them? And should we attempt to secure the directory? C:\Program Files is only writeable by admin users, which presents a security boundary to rogue apps. Tough choices…

    Thanks,…

    anonymous commented  · 

    We're still here 2017 going into 2018... ResidentSleeper

  4. 415 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Visual Studio IDE » IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →
    anonymous commented  · 

    Yes we totally need support for editing this in Visual Studio. I still want to type check it and be able to compile it, before deploying.

  5. 677 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  Visual Studio IDE » Languages - Visual Basic  ·  Flag idea as inappropriate…  ·  Admin →
  6. 104 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
  7. 1,809 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    anonymous commented  · 

    Why deprecate something so handy to use

  8. 809 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    anonymous supported this idea  · 
  9. 14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    anonymous supported this idea  · 
    anonymous commented  · 

    "Just so you know, $499 is our list price for TFS CALs, but you may be able to get a better price from your software reseller depending on your purchase quantities and the Microsoft Volume Licensing programs your organization qualifies for" -->

    Just so everyone else knows, even if your one of the big boys you will still be slugged >$200 per TFS Client CAL.
    Oh and the equivelant functionality for a SVN or GIT non developer (i.e. Eclipse user that is doing testing, scripting, documentation or any other task that doesn't require Visual Studio)
    --> $0

Feedback and Knowledge Base