Visual Studio 2010 Beta 2 Known Issues
[This is Part 1. Read Part 2 here ]
Now that we’ve shipped Beta2 and the world is busy downloading the fresh new bits, I’m very excited to know what do you guys think? Will you like it? Will there be major issues that we missed? Time will show :)
- http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx – the Beta 2 start page
- http://connect.microsoft.com/visualstudio/feedback – official feedback channel
By definition, this Beta 2 release is not final, and there are still bugs lurking around out there. We are very busy fixing those bugs for RTM, but for now, there are some that we haven’t had time to fix before Beta2.
This post lists some of the known issues that are in VS 2010 Beta 2. It’s not in my powers to maintain a comprehensive list here, I’ll just mention the ones which I was personally involved with in my day-to-day work. Apologies that I have found them too late, but I guess better late then never...
Updates – new!
Posted the Part 2 of the issues (updated 11/12/2009)
All further updates will happen there or will wait until Part 3.
The official Beta2 known issues list (updated 10/26/2009)
Updating the .sln file from Beta1 to Beta2 (updated 10/26/2009)
Need to upgrade .sln file from Beta2 in order to be able to double-click it. See Jon’s post here for more details:
Setup dialog UI layout wrong on High DPI
Embarrassing! Unfortunately, not everyone on the Visual Studio team is rigorous about non-default testing, such as High DPI, Accessibility, etc. We will hopefully fix this one before RTM. Also recent data shows that non-96 DPI is a very common setting, a lot of people actually use 120 DPI and others. I personally use 120 DPI, that’s how I find these bugs.
SmartTag high DPI issues
With high DPI, the SmartTag menu is missing horizontal menu separator bars. Also the right vertical edge of the SmartTag button disappears. These bugs are a recent regression from WPF introducing the UseLayoutRounding API. The WPF team is looking into fixing these issues before the release.
QuickInfo tooltip trimmed at high DPI
This is another regression from the new DWrite technology. The last word in the tooltip is missing! This one is fixed already.
Thin line on top of the active document tab
Again, another high DPI issue. You can only notice this one if you look closely. We’ve fixed this already as well.
Outlining Expand/Collapse glyphs are shifted several pixels up
Fixed already. A lot of people complained about this internally.
Zoom combobox in the bottom-left corner of the editor isn’t aligned with the horizontal scrollbar
This is fixed.
Don’t tear off the Call Hierarchy tool window!
When you try to undock the C# Call Hierarchy toolwindow and drag it away (for example, to another monitor), VS will crash. This one is too embarrassing, because I was the one who is responsible for testing Call Hierarchy. To my defense, I was on vacation when this regressed and when I came back and found this, it was too late to fix. Shell UI team changed something about the WPF toolwindow implementation and we had some layout logic that didn’t expect double.Infinity as an argument, so we crashed. This one’s already fixed in recent builds.
Vertical separator bar in the Call Hierarchy tool window doesn’t resize the details pane
This also only reproes under 120 DPI and above. You can’t resize the two panes below by dragging the vertical bar:
And again, this is one that I should have caught and missed. When I caught this, it was too late to fix for Beta2. The WPF team is looking at this one right now.
Error message connecting to a TFS server via HTTPS
Well, guess what, the TFS client team has done it again! TFS HTTPS story was broken in Beta1, and it still has a bug in Beta2. However the good news is that there is a really easy workaround this time.
When adding a new TFS HTTPS webserver (e.g. a Codeplex server at http://codeplex.com), after entering your credentials you will see this:
Don’t panic! Just enter your credentials again and things will work just fine. If you used the Tip (http://blogs.msdn.com/kirillosenkov/archive/2009/09/27/tip-don-t-enter-your-codeplex-credentials-every-time.aspx), then you will be unaffected by this and things will hopefully run smoothly.
Ctrl+Alt+DOWN ARROW doesn’t bring up the active document list
Ctrl+Alt+Down used to bring up the active document list, in Beta2 it doesn’t. This is fixed.
Start Page: scroll wheel doesn’t work at the news feed
Also the scrollbar thumb only moves in discrete steps. The Shell UI team decided not to fix this, because they don’t have time and resources for this. I actually was surprised to discover that the scrollbar didn’t work in 2008 either. Never noticed this until recently.
VS Command prompt shortcut is not getting installed if you don’t install C++
This one will be fixed as well.
Hovering over ‘var’ during debugging doesn’t show the inferred type
Jeffrey Richter told me about this minor annoyance. Although our language service correctly reports the inferred type when you hover the mouse cursor over ‘var’ in design time, it doesn’t work in debug mode. Since Jeff teaches a lot of courses in debugging and threading, this was bugging him ever since we shipped C# 3.0. Well, we finally fixed it for 2010 RTM. Thanks to Jeff for reporting this!
Visual Studio doesn’t start maximized when first launched
A while back I’ve logged a bug against the Shell team to “just start VS maximized for heaven’s sake”. They did the fix, but somehow it didn’t make it into the Beta2 branch. They’ll hopefully fix this for RTM.
Well, these were the ones worth mentioning I guess. Apologies if you run into any of these or any other bugs for that matter. I will keep updating this post with more issues that I find or I think users should be aware of. Please keep in mind that this is an unofficial list.
Please do let us know about any issues you find by submitting a connect bug. If the bug/suggestion/feedback is related to the C# language or IDE, also feel free to let me know directly or leave a comment on this blog. Since I work closely with the VS editor team, it’s worth watching their blog and giving them feedback: http://blogs.msdn.com/vseditor. Also, if you have any feedback about the new text rendering in WPF 4.0 and Visual Studio, the WPF Text team has a blog here: http://blogs.msdn.com/text.