336 votesGary Harper supported this idea ·
I am fine with a separate toolkit as long as it can be seamlessly used with Visual Studio. I don't want to have to bounce back and forth between toolsets to update some button size or text. I also want to use something that Microsoft supports so that when new versions of Visual Studio or the UI toolkit are release, they work together. As long as their is some sort of partnership I am open to it. But, I don't want to go down the path of adopting some toolkit that becomes deprecated due to a change in Microsoft's plans.
"The ONLY but very little advantage may be, that beginners can better read it over C# - but this it."
Private mIntList as New List(Of Integer)? What kind of nonsense is that?
List<int> for the win.
Does not work if you #ifdef across methods.
I always want to save changes because now and then the application will crash or hang Visual Studio. It wouldn't hurt to have options, though.
38 votes6 comments · Azure DevOps (formerly Visual Studio Team Services) » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
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.