VS2010 Beta 2 Feedback Survey
Last week we shipped Beta 2 for broad distribution. Many of you have already sent us comments and improvement suggestions (thanks!)
At this point we are down to our final set of bug fixing, perf tuning, etc. I’m very much interested in your feedback so we can take action on it before we ship the final version. To help make it easy, you can take this simple survey.
One thing in particular I am hearing a lot of feedback on is performance. We are working hard on the next round of perf improvements. You can supply your feedback through the survey. When you give us your feedback, the more actionable you can make it the better. We need to know what operations you are doing (like editing, debugging, etc), what kind of hardware you have (CPU, RAM, disk), and your hosting scenario (main machine, running in VM, terminal server, etc).
thanks in advance for your feedback!
Jason
Comments
Anonymous
October 29, 2009
There seems to be a major disconnect between the evangelists, such as yourself, and the people who actual handle bug reports and feature requests on Connect. You ask for feedback, but the people who run Connect close many reports as won't fix or by design. Sometimes, they focus only on the work around without acknowledging a reproducible bug. The amount of goodwill Microsoft has squandered in the developer community is nothing short of stunning. A big result of this is very experienced developers are either not participating in this beta or they are quitting the beta program out of frustration. I am quite close to the latter. (I ran across a splitter window bug. It's similar to one I filed before, but I already know that after a professed confusion about what I mean, it will be declared "by design" though if someone actually did design it that way they're pretty dumb. End result, I've decided to not bother filing it. It's just not worth the aggravation.)Anonymous
October 29, 2009
@Joe - I actually run the engineering team so I'll take the blame for the Connect responses (my folks). We are in the process of tracking all the Connect bug feedback right now and will be working to resolve issues. Thanks for providing your feedback through the system. If you have some examples that are really bugging you, please do send me the connect ID and I will follow up. thanks, JasonAnonymous
October 29, 2009
The comment has been removedAnonymous
October 29, 2009
Hey Jason, What about this bug: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=499420Anonymous
October 29, 2009
One extreme oddity about Connect is the inability for others to see screen shots (or any attachments). When I create Beta 2 bugs on Connect that involve the UI, I attach screen shots for 2 reasons - 1) obviously, I hope it will help the team that gets the bug assigned to them in understanding the bug and 2) I want other users to be able to see the screen shots to confirm that a bug they're seeing is (or more importantly, isn't) the same bug I filed. In using bugzilla, trac, TFS since before V1 RTM, etc. I've never had a system I've used that didn't let others see the screen shots posted. Even the systems (like RedHat's internal bugzilla) that had support for "private" bugs (not viewable by the public) still had the concept of public bugs. Not having any option for attachments to be viewable (not even by the person that filed it, funny enough) is bizarre. Yet, Connect has considered this By Design for 4+ years now: https://connect.microsoft.com/Connect/Feedback #3 most up-voted active bug #3 most up-voted active suggestion Any chance you can make some forward progress on this? If Connect isn't going to move forward on something like this, I'd frankly rather file VS bugs on codeplex where at least I get a real TFS interface and can do something like view the attachments to bugs :)Anonymous
October 31, 2009
i have an error, If i run my website in visual studio 2005, unable to connect to visual studio's localhost web server error is handled wht can i do for that ?Anonymous
November 02, 2009
Here is a good example of a really lousy response on Connect: <a href="https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=504714">https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=504714</a> Ironically, the issue is probably by design, but not for the reasons given. It appears that the static CRT and MFC release libraries have debug information turned on. I assume that this is also why performance testing has shown VS 2010 to be 20%+ slower in optimized release builds vs VS 2005/2008 (for my tests--may not be true across the board.)Anonymous
November 02, 2009
Another one: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=357967 Still hasn't been fixed. Just how lazy are you people? And don't you care that you look stupid and lazy? And who is it that still insists on adding a comment at the top of every file that restates the file name? (And while ranting; who came up with having stdafx.h include targetver.h which now includes SDKDDKVer.h? Do you have a department there that comes up with ways to make things complicated for no reason? Don't get me wrong; SDKDDKVer.h is long overdue, but why not have stdafx.h include it directly? More importantly, someone had the time to change the wizards to do something utterly useless, but not anything more.)Anonymous
November 02, 2009
And one more: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=357962 This still isn't fixed.Anonymous
November 02, 2009
I just installed the Beta 2 and am running under 64 bit Windows 7. When I try to access the 'View' menu, the entire IDE crashes. I posted a bug report on the Microsoft Connect site, but looking for more immediate gratification, you know how it is, right?Anonymous
November 02, 2009
The comment has been removedAnonymous
November 03, 2009
The comment has been removedAnonymous
November 03, 2009
The comment has been removedAnonymous
November 04, 2009
The comment has been removedAnonymous
November 04, 2009
The comment has been removedAnonymous
November 04, 2009
@Ryan I was also slightly disappointed that we lost the drag and drop customisation on the toolbars. However, it's only something I customise once after a fresh install, so it's not too painful, but it would be nice to have this back in a future release. I totally understand the pain of switching to WPF and finding it doesn't support many of the basic features that we could previously take for granted. The dire state of WPF (e.g. poor design time experience, loss of productivity etc.) is one of the reasons so many people are avioding it like the plague. Hopefully we can also have a real shake up of the WPF controls in the next release in order to improve some of these types of scenarios.Anonymous
November 05, 2009
The comment has been removedAnonymous
November 05, 2009
@Fernando Could you please provide more details on the specific differences you are seeing in the stepping behavior between VS 2008 and 2010? Do you have a specific for-loop that demonstrates the issue you are talking about?Anonymous
November 05, 2009
The comment has been removedAnonymous
November 05, 2009
The comment has been removedAnonymous
November 10, 2009
When editing a C++ source file, there is a useful command in context menu: Go To Header File. After running this command and switching to .h, I was confused - where is the pair to this command, namely "Go To Source File"?Anonymous
November 10, 2009
@Dmitry - Header files can be included in multiple source files so in a typical case there is no one source file to go back to...Anonymous
November 16, 2009
@Dmitry - To add to what Jason said, you can use Navigate Backward to accomplish this 'backwards leap', unfortunately if you have moved around extensively in the header it will take you to all previous cursor locations before taking you back to the C++ file. But if you just pop from C++ file to header then Navigate Backwards should take you back to the C++ file you came from.Anonymous
November 16, 2009
The comment has been removedAnonymous
November 17, 2009
@Hitesh - These are good suggestions. Could you file a Connect bug for this so that we can track it for future VS releases? Here is the Connect site: http://beta.microsoft.com/default.aspxAnonymous
November 17, 2009
while installing vs2010 beta2 on my windowsXp sp2 i am getting error informing "attempt failed to install windows installer 4.5" so i manually downloaded it from microsoft and installed. it is again giving the same error.... whats the reason? thanx in advance if u could help in someway...Anonymous
November 18, 2009
Hi @Chakradhar, This is an interesting issue with MSI4.5. In order to help you further, I want to look at your setup logs. Please run the <a href="http://go.microsoft.com/?LinkId=8967044">collect tool</a> to collect the setup logs. Then please upload them to somplace like <a href="http://skydrive.live.com/">Windows LiveTM SkyDrive</a> or http://www.file-upload.net/. Then send a link to me at aaronru(a)microsoft_dot_com. Thanks! Aaron Ruckman MSFTAnonymous
November 19, 2009
ya the problem was it was not downloaded properly..again i downloaded and installed its working fine..but to install documentation should i have internet connection compulsory.....and give me one url where i can provide feedback......Anonymous
November 19, 2009
The comment has been removedAnonymous
November 23, 2009
@Chakradhar Re: "one URL where I can provide feedback", please log all your feedback on the Connect website: http://connect.microsoft.com/VisualStudio Your feedback will be routed to the appropriate team.Anonymous
November 23, 2009
Hi, VS2008 Context Menu: Go To Header File. If *.h and *.cpp files are in different directories, then "Go To Header File" don't work. Why? ex: D:ProjectExternalHomeFooClass.h D:ProjectDllHomeFooClass.cpp ThanksAnonymous
November 24, 2009
Hi @Chakradhar, I'd like to understand more about the toolbox slow-down issue (may or may not be performance related). Let's discuss it in details offline. My email address is wenbinx@microsoft.com. In addition, you could follow the tips from Richa to log the issue via Microsoft Connect site at http://connect.microsoft.com/VisualStudio, provided you've done so yet. Regards, Wenbin MSFT