vscoloroutput Issue Tracker Rss Feed

Commented Issue: Upgraded from 1.42 to 1.43 and now my background is dark but settings still show defaults [7]

Zodman — Tue, 05 Mar 2013 03:19:40 GMT

Upgraded from 1.42 to 1.43 and now my background is dark but settings still show default light colors
VS2010 SP1
Something broke...

Comments: I think more recent versions resolve the problem. Looks like the latest version isn't available through VS Extension Manager (at the time of writing, 1.4.5 was available from CodePlex but only 1.4.3 was available via VS Extension Manager). Download the VSIX from CodePlex and install that version.

Commented Issue: Coloring find results does not work [10]

HipCzeck — Thu, 06 Dec 2012 16:47:06 GMT

I'm using VSColorOutput 1.4.3. It works great for build output, but it does not for find results. The colors are configured (some gray for the file name and purple for the search term), but the text is all black.

I'm running a German-language version of Visual Studio 2010 SP1, and in FindResultsClassifier.cs, there are several hard-coded English strings (I guess to find out if you're in the find results window), like "Find All", "Match case", "Whole word" and "List filenames only". Since these are in German in my installation, I guess you just don't recognize that you're going through search results. Maybe you can get the localized strings from Visual Studio at runtime?
Comments: Similarly, my hyperlinks in the find window aren't applying the custom Uri hyperlink style color. In my dark theme, they are both a nearly unreadable Navy Blue on dark grey.

Commented Issue: VS 2012 not supported by 1.4.5 version [12]

volk — Wed, 28 Nov 2012 16:45:13 GMT

I have tried to install versions 1.4.4 and 1.4.5 downloaded from CodePlex, and it looks like Visual Studio 2012 is not supported. I have attached installation log, which states that only different editions of VS 2010 are supported.

Version 1.4.3 from VS Gallery works fine with VS 2012.
Comments: Apparently this is already being discussed: https://vscoloroutput.codeplex.com/discussions/394127

Created Issue: VS 2012 not supported by 1.4.5 version [12]

volk — Wed, 28 Nov 2012 16:35:00 GMT

Created Issue: Support ansi color codes? [11]

moswald — Wed, 21 Nov 2012 20:26:15 GMT

Any chance you could add a feature to support ANSI color codes?

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

Zodman — Wed, 07 Nov 2012 02:58:27 GMT

Thanks for one of the greatest Visual Studio extensions ever!

I'm using VSColorOutput together VSCommands 10 on Visual Studio 2010 SP1. Everything worked flawlessly until the update of VSColorOutput from 1.4.2 to 1.4.3. Since that update I get the following messages each time I start Visual Studio:
"Visual Studio has encountered an exception. This may be caused by an extension"

Despite this message both extensions seem to run like expected when working with a project.

Configurations I've already tested:
- disabling VSCommands leaving VSColorOutput enabled: works
- disabling VSColorOutput leaving VSCommands enabled: works also
- downgrading VSColorOutput back to 1.4.2 and leaving VSCommands enabled: works
- upgrading VSColorOutput to 1.4.3 and leaving VSCommands enabled: yields above exception message
Comments: Extension Manager in VS gives you version 1.4.3 which contains this issue. Installing 1.4.5 from codeplex, resolves the issue. The newer version needs to be surfaced in Extension Manager to prevent this issue being so widespread.

Commented Issue: Issue with latest version of VSColorOutput [8]

jeroenheijmans — Tue, 11 Sep 2012 17:51:55 GMT

Ever since VSColorOutput updated I have the following colors in my output window. (see attachment).
Comments: +1 Same issue for me, dark gray background on Visual Studio 2010 / Win7 64b. Not sure what triggered this to happen, as far as I know I didn't upgrade or change anything in my setup. Found a workaround though: 1. Go to Tools > Options > Environment > Fonts and Colors. 2. In the "Display items:" area, scroll down to the VSColorOutput entries. 3. Change the "Item Background" from "Default" to "White" on all of them. 4. Restart Visual Studio. > Result: readable VSColorOutput awesomeness! Screenshot for workaround attached.

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

BenWalby — Tue, 10 Jul 2012 08:41:01 GMT

Thanks for one of the greatest Visual Studio extensions ever!

I'm using VSColorOutput together VSCommands 10 on Visual Studio 2010 SP1. Everything worked flawlessly until the update of VSColorOutput from 1.4.2 to 1.4.3. Since that update I get the following messages each time I start Visual Studio:
"Visual Studio has encountered an exception. This may be caused by an extension"

Despite this message both extensions seem to run like expected when working with a project.

Configurations I've already tested:
- disabling VSCommands leaving VSColorOutput enabled: works
- disabling VSColorOutput leaving VSCommands enabled: works also
- downgrading VSColorOutput back to 1.4.2 and leaving VSCommands enabled: works
- upgrading VSColorOutput to 1.4.3 and leaving VSCommands enabled: yields above exception message
Comments: I get the same error message on start-up (it's worth noting I have disabled all other extensions and still receive this error message).

Commented Issue: Coloring find results does not work [10]

yfital — Wed, 27 Jun 2012 14:24:03 GMT

I'm using VSColorOutput 1.4.3. It works great for build output, but it does not for find results. The colors are configured (some gray for the file name and purple for the search term), but the text is all black.

I'm running a German-language version of Visual Studio 2010 SP1, and in FindResultsClassifier.cs, there are several hard-coded English strings (I guess to find out if you're in the find results window), like "Find All", "Match case", "Whole word" and "List filenames only". Since these are in German in my installation, I guess you just don't recognize that you're going through search results. Maybe you can get the localized strings from Visual Studio at runtime?
Comments: The same behavior is happening on an english version VS2010 sp1

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

Cpt_Kork — Mon, 18 Jun 2012 06:15:56 GMT

Thanks for one of the greatest Visual Studio extensions ever!

I'm using VSColorOutput together VSCommands 10 on Visual Studio 2010 SP1. Everything worked flawlessly until the update of VSColorOutput from 1.4.2 to 1.4.3. Since that update I get the following messages each time I start Visual Studio:
"Visual Studio has encountered an exception. This may be caused by an extension"

Despite this message both extensions seem to run like expected when working with a project.

Configurations I've already tested:
- disabling VSCommands leaving VSColorOutput enabled: works
- disabling VSColorOutput leaving VSCommands enabled: works also
- downgrading VSColorOutput back to 1.4.2 and leaving VSCommands enabled: works
- upgrading VSColorOutput to 1.4.3 and leaving VSCommands enabled: yields above exception message
Comments: It would be actually very nice to get rid of the frequently reappearing exceptions.

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

codekaizen — Mon, 18 Jun 2012 03:25:59 GMT

Thanks for one of the greatest Visual Studio extensions ever!

I'm using VSColorOutput together VSCommands 10 on Visual Studio 2010 SP1. Everything worked flawlessly until the update of VSColorOutput from 1.4.2 to 1.4.3. Since that update I get the following messages each time I start Visual Studio:
"Visual Studio has encountered an exception. This may be caused by an extension"

Despite this message both extensions seem to run like expected when working with a project.

Configurations I've already tested:
- disabling VSCommands leaving VSColorOutput enabled: works
- disabling VSColorOutput leaving VSCommands enabled: works also
- downgrading VSColorOutput back to 1.4.2 and leaving VSCommands enabled: works
- upgrading VSColorOutput to 1.4.3 and leaving VSCommands enabled: yields above exception message
Comments: All: note that I have submitted a pull request which presumes to fix this issue. Please try it and test it out to ensure it does indeed resolve this issue.

Commented Issue: Issue with latest version of VSColorOutput [8]

FallenGameR — Thu, 14 Jun 2012 21:47:34 GMT

Ever since VSColorOutput updated I have the following colors in my output window. (see attachment).
Comments: Same issue. Background color is not dark. VS 2010.

Commented Issue: Coloring find results does not work [10]

GrzegorzKozub — Fri, 08 Jun 2012 10:55:43 GMT

I'm using VSColorOutput 1.4.3. It works great for build output, but it does not for find results. The colors are configured (some gray for the file name and purple for the search term), but the text is all black.

I'm running a German-language version of Visual Studio 2010 SP1, and in FindResultsClassifier.cs, there are several hard-coded English strings (I guess to find out if you're in the find results window), like "Find All", "Match case", "Whole word" and "List filenames only". Since these are in German in my installation, I guess you just don't recognize that you're going through search results. Maybe you can get the localized strings from Visual Studio at runtime?
Comments: For me the Find Results coloring always applies the default VSColorOutput colors but never the ones I've set up in Options - Environment - Fonts and Colors - Text Editor - VSColorOutput Find Results *. Tested on Visual Studio 2010 SP1 as well as 2012 RC.

Created Issue: Coloring find results does not work [10]

OregonGhost — Mon, 04 Jun 2012 08:48:19 GMT

Commented Issue: Upgraded from 1.42 to 1.43 and now my background is dark but settings still show defaults [7]

xuefer — Tue, 22 May 2012 08:17:31 GMT

Upgraded from 1.42 to 1.43 and now my background is dark but settings still show default light colors
VS2010 SP1
Something broke...

Comments: i can reproduce this issue after installed Subversion - ankhSVN. when devenv is open, output window "show output from" drop down list is default to ankhSVN(or vmware in previous report), maybe this is the problem. when build, it switch to "build", and maybe background color is not initialized there?

Commented Issue: Upgraded from 1.42 to 1.43 and now my background is dark but settings still show defaults [7]

xuefer — Thu, 17 May 2012 07:09:21 GMT

Upgraded from 1.42 to 1.43 and now my background is dark but settings still show default light colors
VS2010 SP1
Something broke...

Comments: i can reproduce this issue by checking plugin for visualstudio when i install vmware 8. and not reproduce if it re-run vmware 8 setup -> modify -> uncheck it

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

Fulg — Mon, 30 Apr 2012 15:30:26 GMT

Thanks for one of the greatest Visual Studio extensions ever!

I'm using VSColorOutput together VSCommands 10 on Visual Studio 2010 SP1. Everything worked flawlessly until the update of VSColorOutput from 1.4.2 to 1.4.3. Since that update I get the following messages each time I start Visual Studio:
"Visual Studio has encountered an exception. This may be caused by an extension"

Despite this message both extensions seem to run like expected when working with a project.

Configurations I've already tested:
- disabling VSCommands leaving VSColorOutput enabled: works
- disabling VSColorOutput leaving VSCommands enabled: works also
- downgrading VSColorOutput back to 1.4.2 and leaving VSCommands enabled: works
- upgrading VSColorOutput to 1.4.3 and leaving VSCommands enabled: yields above exception message
Comments: I have the same issue + callstack with PowerCommands installed, which seems to do similar things to VSCommands...

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

blueonion — Wed, 25 Apr 2012 12:24:21 GMT

Thanks for one of the greatest Visual Studio extensions ever!

I'm using VSColorOutput together VSCommands 10 on Visual Studio 2010 SP1. Everything worked flawlessly until the update of VSColorOutput from 1.4.2 to 1.4.3. Since that update I get the following messages each time I start Visual Studio:
"Visual Studio has encountered an exception. This may be caused by an extension"

Despite this message both extensions seem to run like expected when working with a project.

Configurations I've already tested:
- disabling VSCommands leaving VSColorOutput enabled: works
- disabling VSColorOutput leaving VSCommands enabled: works also
- downgrading VSColorOutput back to 1.4.2 and leaving VSCommands enabled: works
- upgrading VSColorOutput to 1.4.3 and leaving VSCommands enabled: yields above exception message
Comments: Looks like the bug was "always" there (race condition). I'll pull this fix into the build once I get my VS 2010 working again. I've had a number of issues ever since I installed VS 11 Beta that have kept me from working on this.

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

Cpt_Kork — Wed, 25 Apr 2012 04:31:27 GMT

Commented Issue: Exception on Visual Studio startup with v1.4.3 [9]

codekaizen — Tue, 24 Apr 2012 23:27:50 GMT

Thanks for one of the greatest Visual Studio extensions ever!

I'm using VSColorOutput together VSCommands 10 on Visual Studio 2010 SP1. Everything worked flawlessly until the update of VSColorOutput from 1.4.2 to 1.4.3. Since that update I get the following messages each time I start Visual Studio:
"Visual Studio has encountered an exception. This may be caused by an extension"

Despite this message both extensions seem to run like expected when working with a project.

Configurations I've already tested:
- disabling VSCommands leaving VSColorOutput enabled: works
- disabling VSColorOutput leaving VSCommands enabled: works also
- downgrading VSColorOutput back to 1.4.2 and leaving VSCommands enabled: works
- upgrading VSColorOutput to 1.4.3 and leaving VSCommands enabled: yields above exception message
Comments: Fixed with pull request http://vscoloroutput.codeplex.com/SourceControl/network/forks/codekaizen/VSColorOutputBugFixes/contribution/2117