– Lack of clarity, why can’t you say which version has a fix in. If a bug is a serious bug, it should be prioritised by management, with technical input, votes should not play a part in it, if my app crashes due to a null pointer deref in the CRT, it’s a bug, irrespective of number of votes.
– Stupid comments about voting on bugfixes. I’ve seen this issue countless times, where people say they need a fix in VS 2017 and it gets ignored. – Lack of understanding of urgency – if there is a showstopping bug for a customer in VS 2017, it may well for multitudinous reasons be possible for them to NOT try a fix in the latest VS 2019 issue.
– Endless requests for sample code – developers have normally already given sample code. Far too often there are examples of one or more of the following: I hate to say it, but I know I speak for hundreds if not thousands of developers, but the best thing you could to improve VS is:ġ) Greatly improve the support staff dealing with bug reports. I can’t even fathom how many man-years of development resources have been spent over the years trying to kludge around this issue rather than addressing the root cause. You know, I know, and everyone knows what you need to do to properly fix VS performance. My vote is that you outsource development of MSDN to an external company- it’ll probably be cheaper and you’ll get more competent people working on it.Īlso, depressing to see you guys still listing “Improve performance opening and working with large solutions” on your roadmap a place where its been for eons. I just don’t understand why MSDN continues to be such an embarrassment of a website after all of these years of you guys rebuilding it over and over again. There used to be a buried link somewhere in the dev community page to navigate over to the features section that you could click after you had first navigated to the problems section- that’s gone now, and this link,, doesn’t work either because whoever builds your website doesn’t seem to know about standard REST either. The link in your blog post doesn’t actually take you to a page that browses features. Someone managed to take a broken, barely usable website and make it totally unusable. It seems to be impossible to browse through the VS feature suggestions on the web now. In that light, we’d highly appreciate if you would take a brief survey to let us know how to best handle the roadmap going forward. We aim to publish updates more frequently going forward and we’re putting processes in place to make that happen.
We often get feedback on the importance of an up-to-date roadmap for Visual Studio. If there are features that are particularly important to you, please be sure to vote and comment on the features in the Developer Community portal. These features and time frames represent our current plans but may change based on what we learn. Our roadmap is driven largely by what we learn through ongoing customer research, as well as the feedback we get via our Developer Community portal. Our goal is to clarify what’s coming so you can plan for upgrades and provide feedback on which features would make Visual Studio a more productive development environment for you and your team. It captures significant capabilities that we plan to add, but it’s not a comprehensive feature list. The Visual Studio roadmap has been updated to provide a peek into the work planned for Visual Studio through June 2020.
0 kommentar(er)
