SamCPP

My feedback

  1. 83 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Visual Studio IDE » SQL Server and Data Tools  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP commented  · 

    There's no reason for it to not work on Win7. LocalDb works on Win7 and it has the 2016 engine. Microsoft this is a poor decision. Please remove the artificial blockers from SQL 2016.

    SamCPP supported this idea  · 
  2. 45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Visual Studio IDE » Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  3. 201 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.

    Ewald Hofman

    SamCPP commented  · 

    Gyula Solution Explorer is not necessarily a physical representation of the disk structure. This is very common so Solution Explorer could have a different organisation for files. Additionally you can have linked files (same physical file in multiple projects) for example. There are lots of reasons why this would be extremely handy.

    SamCPP supported this idea  · 
  4. 521 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP supported this idea  · 
  5. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Visual Studio IDE » Install  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP supported this idea  · 
  6. 271 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Visual Studio IDE » Project  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP commented  · 

    +1 VSCommands ftw

  7. 6,174 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    112 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP commented  · 

    Silverlight is almost certainly dead. IE's replacement Edge does not support Silverlight at all. Chrome has NPAPI disabled by default and will remove it altogether by end of year (Silverlight and Java applets require NPAPI support in your browser). Firefox is sure to follow suit in due course. That means existing Silverlight has a pretty short future from now.

  8. 2,954 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    111 comments  ·  Visual Studio IDE » Install  ·  Flag idea as inappropriate…  ·  Admin →

    I wanted to update the status to make sure you know that we hear you. This isn’t straightforward to deliver for obvious reasons: Visual Studio installs a disparate variety of tools, runtimes and SDKs, many of which come from third parties or other parts of Microsoft. We recognize that developers would love to see something lighter and while we have nothing new to announce at this stage, we are spending a lot of time thinking about how we can improve Visual Studio installation.

    Thanks for the feedback!

    Tim Sneath | Visual Studio Team

    SamCPP supported this idea  · 
  9. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP commented  · 

    Are you running a 64-bit program?

  10. 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…

    SamCPP commented  · 

    Yes this is a big thorn in WPF productivity.

    SamCPP supported this idea  · 
  11. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP commented  · 

    Yes was just discussing with a colleague. Seems like such a simple thing - it's a bit surprising that is missing.

  12. 391 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP supported this idea  · 
  13. 990 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Visual Studio IDE » Project  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP supported this idea  · 
    SamCPP commented  · 

    "This applies to all project xml files, but in particular to SLN & RESX"

    Indeed. There really should be a base ordering to components in resx, XML in anything generated by VS. In a multi-developer environment, a designer change that scrambles the designer contents makes the designer very difficult to use. Wastes hours every single merge.

  14. 202 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP commented  · 

    Workaround: Find/replace in files can be used to do this.

  15. 190 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    SamCPP commented  · 

    You have the array functions:
    http://msdn.microsoft.com/en-us/library/system.array_methods.aspx

    Is there something outside those?

    SamCPP commented  · 

    Really not sure what you are gaining by this. What's wrong with getting an array?

Feedback and Knowledge Base