131 votes18 comments · Visual Studio Team Services » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
I’m resetting the status of this suggestion. As the comments note, we have not yet implemented syntax highlighting for code blocks in markdown files.
I have merged the duplicate suggestion that was opened with this suggestion. (Duplicate: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/10238214-add-syntax-highlighting-to-parsed-markdown-in-visu).
It is implemented, here is the syntax to use:
185 votes36 comments · Visual Studio Team Services » Work Item Tracking · Flag idea as inappropriate… · Admin →
We would love to make comments editable, but that is harder than you would expect. A comment is tied to a revision and we need to keep the revision immutable because of auditing requirements. But it is on our list but don’t expect anything soon.
33 votes3 comments · Visual Studio Team Services » Work Item Tracking · Flag idea as inappropriate… · Admin →
1 voteAnonymous shared this idea ·
Anything but xaml!!!!
the decisions made by the analyzer are not always correct. means you have to live with the lightbulbs for ever. extremely annoying.
the lightbulb pop ups are extremely annoying and it is breathtaking that Microsoft adds a productivity threat without offering the option to disable it. we consider vs2015 d.o.a. until such time when this functionality can be disabled.
getting rid of the squiggles helps, unscrewing the light bulb would be best. lights up in most of my programs but the programs compile and run error free. I guess one has to be a certified Microsoft genius to understand this feature.
153 votes28 comments · Visual Studio Team Services » Administration & Licensing · Flag idea as inappropriate… · Admin →
22 votes3 comments · Visual Studio Team Services » Work Item Tracking · Flag idea as inappropriate… · Admin →
This is something I'm also looking forward for. It's not good that Web Access is not able to format Date while VS Team Explorer based client is able to handle the same.
998 votes64 comments · Visual Studio Team Services » Version Control (Git/TFVC) · Flag idea as inappropriate… · Admin →
We have a lot of investment taking place on our code review platform that will enable iterative code reviews, and we will initially bring that functionality to Git (via pull requests). Improving iterative code reviews for TFVC is still on our backlog, but it is not in our 6 month plan, so we are resetting the status.
150 votes10 comments · Visual Studio Team Services » Work Item Tracking · 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.
We also want to do this. I think this is rather a common practice. TBH I am very surprised that it cannot be done already.
Thanks for the feedback, we are currently investigating what performance improvements we could make to give you a faster experience when debugging, particularly when the call stack walking is causing the slowness.
See the following blog posts that offers more details on what settings and windows relate to this, and other tips and tricks for speeding up debugging in general. http://blogs.msdn.com/b/visualstudioalm/archive/2015/03/03/make-debugging-faster-with-visual-studio.aspx
Program Manager, Visual Studio Debugger