Search

Visual Studio 2012 Returns invalid DTE.Properties FontAndColors information when switching themes by Blake A Niemyjski

Closed
as Fixed Help for as Fixed

5
0
Sign in
to vote
Type: Bug
ID: 758809
Opened: 8/20/2012 2:46:16 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When you switch from the dark theme to the light theme invalid color settings will be returned via the API. Please see this for more information: http://social.msdn.microsoft.com/Forums/en-US/vsx/thread/ebbcd9dd-636f-47c3-9184-04acb921e181/

I've also created a sample here: http://windowscoding.com/invalidfontsandcolors.zip
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Download and run the sample package (http://windowscoding.com/invalidfontsandcolors.zip). Then look in the output window and then change the theme and verify the incorrect settings in the output window.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Returns invalid font and color information.

Expected results

Should return the correct color information.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Blake A Niemyjski on 10/11/2012 at 9:52 AM
Will this be going out with VS 2012 Update 1? I didn't see it in the CTP3 notes? We will not be implementing the work around as we are awaiting the official patch..
Posted by Microsoft on 10/5/2012 at 4:30 PM
Thanks for the report. I've fixed this in bug and posted a workaround to the forum thread.

-Josh Stevens
VS Shell team
Posted by Blake A Niemyjski on 10/3/2012 at 1:37 PM
Has any progress been made on this?
Posted by Microsoft on 8/21/2012 at 1:25 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 8/20/2012 at 2:53 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.