I would like to be able to review pull requests created in TFS 2015 on Premise. The review should consist of a code review tool that allows me to make comments similar to the way that it works with TFVC when using GIT.

wonderful！wonderful！wonderful！wonderful！wonderful！wonderful！wonderful！wonderful！wonderful！wonderful！

I use F12 quite often to navigate around my code. It opens new source files as "previews" so when I go one level deeper to the next source file then the current one is closed. It would be good to have an option to not open the F12 source files as "previews". I still like the preview feature for when looking for files in the solution explorer, so I don't want to turn it off completely, just for F12 (and similar) code navigation.

Visual Studio code: not to add too much bloat to the slick editor, but a built in runtime for nodejs would allow adding in a diverse and powerful set of tools from the extension store no ?
Without having to configure and maintain a node instance seperately from the editor. Also would allow transporting prefs/settings etc. of node packages across machines (because I want to use VS Code on all my machines/OSs)

Visual Studio Code: already has nice file compare tools. Would be nice to have a way to compare currently edited file with saved version on disk (to quickly answer the question "what did I edit in this" after coming back from a meeting :)

I am a QA engineer new to the .NET/C# world. I noticed that there is a dearth of information available in the test/ test automation world for .NET/C# compared to the Java/Open Source world.

It would be nice of Microsoft or a large user of its technologies would host a physical conference or online webinar to share some best practices.

Please Insert ASM manipulation to vb.net and c#. God bless you!

While I like being able to tear off tabs and drop them onto other windows, I *really* like grouping them (i.e. my repositories are in one window, specifications in another, models in another). It would be easier to switch between them if the Window menu, in addition or instead of the flat window view (which can get unwieldy), show it by named tab groups.

We use conditional compilation symbols a lot and most of the times we need to scroll the textbox to find the word we need to remove. We always have more than 10 compilation symbols and can only see a few of them.

Even enlarging the project property window the textbox doesn't resize.

It's hard to find definitions in code when other entities, like parameters, enum values and region names all share the same colour.

It would very much ease browsing for type member definitions if they would have a distinct setting in Tools > Options > Environment > Fonts and Colors for those.

I propose to have distinct settings for fields, properties and methods, allowing to highlight the corresponding identifier in the definition.

I would very much prefer if class method definitions would be displayed bold, for example. And class field definitions might be displayed in dark blue.

Please include the ability to add a Validation Rule in the "Create Data Binding..." dialog.

Currently a Validation Rule can only be added to a binding by editing the XAML directly, using element syntax.

To make matters worse the validation rule is deleted if the binding is subsequently modified within Blend.

On the left side there is a column beside the coding window.
There you can set breakpoints, enable and disable them, you can enter a comment.

Now:
I suggest if you left-click a second time there will come the exact same thing in yellow instead of red. (Or offer 3 dropdown icons).
Results in "Inspectionpoint" or "Point of inspection".

Click it a third time makes it green. (Or offer 3 dropdown icons).
Results in "Approvedpoint" or just "Approved".

That's it. Please consider a dicussion about this feature, thanks microsoft.

I wish there was a possibility to attach documents to the code editor. For example,i want attach the flow chart diagram file or picture file to be attached to a method or block of codes.

Thanks.

Capturing Network traffic is really nice idea. But currently it supports only WinRT HttpClient APIs. For ASP.NET & WPF dev this's not at all useful :(

Please add support for capturing traffic from .Net HttpClient and WebClient API as well.

Thanks.

Often I find it frustrating when after debugging that I'm unable to view the exception thrown in the last debug run. This has generally led me to copy-paste the message.

muy pobre en reportes debe uno instalar el crystal reports