Visual C++ 2015 Update 2 Bug Fixes

We’re happy to have shipped Visual Studio 2015 Update 2 (grab a copy here!). This is a quick glance at the Visual C++ bugs resolved that were reported on the Microsoft Connect portal. We have fixed 330 Connect and VS Feedback bugs in the compiler frontend, backend, and libraries; and an additional 30 bugs in the IDE for Visual Studio 2015 Update 2.

These bugs were submitted by the users in the community. Although we didn’t fix every reported customer issue (yet!), we appreciate that our customers take the time to file bugs on our product, and we try to prioritize the bugs that come from the community. If you encounter issues while using our compiler, please file bugs! It helps us know which issues should have the most attention.

Join the conversation

1463904 was fixed for RTM in July 2015, improved in Update 1, but had no
changes for Update 2 (the parser is still confused). 1491794 was fixed
in Update 1 back in November. 2173302 has not been fixed at all and
still crashes the compiler.

And I just checked my own entries in your list. May I suggest you verify
the others?

Good point — the reason that 1463904 came up on the radar is that the developer marked the bug as resolved in the Update 2 time frame. It’s a little involved to track down the history of every bug to verify when the last actual code changes were, but the delay between fixing the bug and marking the bug as resolved is relatively rare for us.

I wish you guys would ditch Connect altogether and use something sane.
We’re all developers here, and we’re using our own time to help you
fix problems.

Fix the synchronization issues, manage the “status” field better
(“none” and “active” seems to be most often used), add notifications,
allow formatting (or use monospace fonts), add a “fixed in version”
field, throw a few servers at it so it doesn’t take 10 seconds to load
the page and add a search feature.

Or just open your internal bug report engine. I’m guessing it has all
of that already.

Btw: many of the connect issues are still not marked as “fixed”. Am I right, that there are synchronization issue between connect and maybe some other platform you use internally (hence we may still see them in open state)?

I believe you’re right about some synchronization issues — the bug you called out has been fixed and resolved recently, but the public connect page doesn’t reflect that.

There are a few bugs that apparently came up in my query for resolved bugs that didn’t make the train for Update 2 (such as the bug you called out). I’m investigating to see the cause for the discrepancy and will update the blog post accordingly when I figure out the cause.

Could you provide some more info about the failures you’re seeing? We’re very interested in fixing bugs that are blockers for customers. If you can give us some info, we’ll make sure it gets to the right people.

Support for variable templates in Update 2 is a disappointment. Not only that one gets invalid syntax highlighting and IntelliSense squiggles in proximity of such constructs (this has been advertised), but also the compiler fails in SFINAE contexts like ‘std::enable_if_t<std::is_xxx_v>’ (as someone has already reported, see https://connect.microsoft.com/VisualStudio/Feedback/Details/2524878).

At random times all text in all text editor windows becomes extremely small and
I have to increase the font size somewhat in:
VS
Tools Menu
Options
Fonts and Colors

I’m now using a font size of 40, which looks as the normal 10.

The search window (Ctrl + F) is extremely small and unusable, no way to increase the size.

The blinking text caret also becomes extremely small and since it has the same color as
the left most text editor window edge, it becomes invisible. To circumvent that I had to increase the size of the text caret a lot in the Windows Control Panel which affects every Windows app.

The small area at the left of the text editor which contains the red breakpoint dots also become very small and hard to use.

I’ve had this problem for some time now and was hopping that update 2 would solve the problem but it didn’t.
So this must be some kind of a settings bug but no idea how to fix it?

This problem is only related to Visual Studio, every other app works OK.

Any fixes forthcoming (or workarounds) for the Git changes bug introduced with Update 2? This is very painful for a lot of us. I’m having to use the Tortoise Git client instead of VS until this gets resolved.