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

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 758809 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 8/20/2012 2:46:16 PM
Access Restriction Public

Description

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
Sign in to post a comment.
Posted by Blake A Niemyjski on 4/29/2014 at 3:26 PM
That's really great that you fixed it in 2013 after introducing it in 2012. However, just telling someone to upgrade is not very easy to do especially when its your customers. It's not like you give Visual Studio away for free.

We have a package that spans multiple VS Versions. Now thankfully we still look really bad to any customers who are using VS2012 as this bug still effects us but wasn't addressed in one of the 4 major updates that were applied to VS2012. Even though 5 others voted on this issue and I spent the time to include a sample.
Posted by Deon [MSFT] on 4/29/2014 at 12:32 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Blake A Niemyjski on 8/19/2013 at 2:35 PM
So This has been fixed in 2013, but due to another bug, it gave these same results. It appears that colorableItems (FontsAndColorsItems) renamed an entry for Highlighted Reference (VS2010/VS2012) to HighlightedReference in 2013. This is somewhat breaking, but an easy fix... Also I noticed that the collection contained 345 entries on my machine with duplicates for


    Line 110: [8/19/2013 4:24:30 PM] Name: Visible Whitespace Background: 16777215 Foreground: 5392404 Bold: False
    Line 285: [8/19/2013 4:24:30 PM] Name: Visible Whitespace Background: 16777215 Foreground: 5392404 Bold: False

    Line 107: [8/19/2013 4:24:30 PM] Name: Track changes before save Background: 55551 Foreground: 14474460 Bold: False
    Line 108: [8/19/2013 4:24:30 PM] Name: Track changes after save Background: 3981845 Foreground: 14474460 Bold: False
    Line 109: [8/19/2013 4:24:30 PM] Name: Track reverted changes Background: 16422239 Foreground: 14474460 Bold: False
    Line 299: [8/19/2013 4:24:30 PM] Name: Track Changes before save Background: 8712943 Foreground: 0 Bold: False
    Line 300: [8/19/2013 4:24:30 PM] Name: Track Changes after save Background: 3175511 Foreground: 0 Bold: False

Someone might want to look into the possibility of this collection containing duplicates.
Posted by Blake A Niemyjski on 8/18/2013 at 8:42 PM
Hello,

This is still a bug with the VS2013 preview. Can you please confirm this is fixed in the preview.
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 Josh [MSFT] 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 Macy [MSFT] 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 Helen [MSFT] 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)