Would vote +3 if I had any votes left...
Would vote on this if I had any left.
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to address this suggestion in a future release. Thanks for capturing the pain points you feel when stepping through multithreaded applications while debugging. We will be providing an update soon.
Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread. If you have other breakpoints in your application and another thread hits one, then you will be debugging in the mixed thread state as described in this item.
Program Manager, Visual Studio
Would vote 3 votes but I'll all out! :(
Support for navigation to C# symbols from F# has been implemented by Vasily Kirichenko and Saul Rennison in our OSS community. The reverse (C# → F#) is something we’re heavily considering for future work.
Phillip Carter, F# PM
NOTE: all .NET projects are generally assembly projects whether they generate executables or dlls.
I like this idea but I'm all out of votes.
Would +1 if I had votes left
+1, but I have no votes left
15 votesunder review · 5 comments · Visual Studio IDE » IDE and Editor · Flag idea as inappropriate… · Admin →
Please take a look at Meld and P4Merge as examples. Both of these are simple and allow for easy to understand yet powerful 2 and 3 way diff/merge.
1,364 votesunder review · 13 comments · Visual Studio IDE » UWP / WPF / XAML Tools · Flag idea as inappropriate… · Admin →
This suggestion should be moved to the VS Performance Forum (http://visualstudio.uservoice.com/forums/131389-visual-studio-performance) or just marked as ACCEPTED so that the votes are returned.
I’m Will Buik, a Technical Product Manager on Visual Studio’s IDE team and I am back with an update. We have added an experimental feature to Visual Studio “15” Preview 5 that improves the time it takes to load Solutions. The feature is disabled by default, but you can turn it on through Tools→Options, “Projects and Solutions”→General→“Lightweight Solution load.”
We would love to hear your feedback about how lightweight Solution load works for you. If you are interested in participating in a quick user study to give us some feedback about the feature please fill out this brief survey: https://aka.ms/w2kt3j. We will reach out to you soon.
If you are interested in learning more about lightweight Solution load, check out the VS Blog: https://blogs.msdn.microsoft.com/visualstudio/2016/10/11/shorter-solution-load-time-in-visual-studio-15/
You can download Visual Studio “15” Preview 5 here – https://www.visualstudio.com/visual-studio-pre-release-downloads/
Thanks everyone, we look forward to your feedback.
I tend to load a solution once ever few weeks. I'm all up for improving the load time but for my own use I can't justify voting for this over some of the other issues.
This is already been improved for Visual Studio 11. I saw it in a video preview and builds no longer block the UI and thus can be stopped easier mid build and such.
When working with a large number of projects in a solution, builds and loading of the solution can become quite slow. We are currently working with around 40 projects and Visual Studio is starting to crawl and this is unfortunate since we are aiming at having possibly over 300 total projects part of the solution due to a modular application design but are afraid of doing so due to performance woes. Making Visual Studio better at handling large projects in terms of performance and also in terms of ease of navigating between projects and their contained files will greatly reduce a barrier to scaling large applications.