The Visual C++ team wants to better understand how you use libraries in your day-to-day development work. Whether you’re publishing libraries, finding libraries that work on the Microsoft platforms for which you’re building your apps, or integrating libraries into your project and build systems, we want to hear from you so we can make the right investments in Visual Studio tooling.
Tell us what works, what doesn’t, and what’s the most important change we could make in Visual Studio to improve how you work with C++ libraries. Is there an open source library you feel is missing from your favorite Microsoft platform? We want to know about it! And yes, there are even some bonus questions about NuGet at the end. :-)
Completing this questionnaire should take about 10 minutes to finish, so take your laptop on your next coffee break and give us an earful.
Click here to go to the survey.
Thank you in advance for taking the time to give us feedback!
I completed the survey. Where/when will the results be published?
how about getting VS dll's or libs bug free so we dont get frustrated?
step1-> Native debugging enabled (C# app)
step2-> do nifty things in C++ code
step3-> sit back and enjoy MS quality
step4-> hope it get fixed in next VS version (not to mention we just paid for 2012 this season and getting desired features and bugfix in a next release. Rapid release, Rapid release, Rapid release, Rapid release, more money, Rapid release, Rapid release, Rapid release, more money, more money...)
More C99 support would be nice. There are more and more C-libraries that are hindered by MSVC (and many have even started to ditch MSVC...).
Making CRT and MFC shipped with VS 2012 backwards compatable with VS 2010 would greatly help. We have to take a lowest/oldest commom MFC/CRT used by any of the 4 different third party DLLs used by our application.
@LS, look for a summary of our findings in about a month or so. The survey will run for a couple weeks, then we will take a few weeks to review and potentially follow up with folks, and then share a summary here on the blog.
Add support for external toolchains (I forgot to put that on my survey)
IE 10 and 11 takes 550ms to perform these basic operations nontroppo.org/.../Hixie_DOM.html (stress testing cases writting some 12 years ago). On same machine, edge version of Chrome takes 27ms.
Here are the try-catch and few other tests: newilk.com/.../SpeedTest1
Reminds me of a quote from Fast and the Furious movie: "It doesn’t matter if you win by an inch or a mile – winning is winning."
That's true. So please apply greedy algorithm here and save every bit where you can to be a winner. We know you can. All you need is to spare some magnificant brians for few hours and you will get sorted it out. For old times sake.. :-)
Make a lib using VS vZ and it can't be used except by others with vZ. Forget about C++. If you don't want to give away source code - and if you are doing this other than a hobby you do not - you can't do it.
All too late, now. How about just fixing bugs. Not dismissing 90% as "tough". Just fix them.
Just improve OpenGL support, please.