VSColorOutput

New Post: Option to select first error in output

neurocod — Tue, 11 Jun 2013 21:46:09 GMT

Nice to add such option, so no need to scroll up to find that error. In VS2010, I used own macro project with such functionality - on BuildEvents_OnBuildDone simply find first message with ": error " and select that line, but VS2012 has no macroses. VSColorOutput seems to be more suitable for this - as it already can parse output messages more precisely.

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

ivanjh — Thu, 06 Jun 2013 02:25:06 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: Opening the 1.4.5 VSIX as a Zip file and changing Version="10.0" to Version="11.0" in extension.vsixmanifest will allow it to install. Your mileage may vary.

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.

New Post: Customise output for specific output.

fhnaseer — Thu, 14 Feb 2013 09:55:37 GMT

I use pre and post build scripts in my projects. I want to customise them. Lets say that my I am copying output files to a directory. So in output it is written that "1 file(s) copied." or "0 file(s) copied."

Now what I want is that if there is text "0 file(s) copied." the color of this line should be red (error) so that I came to know that file is not copied.

How I can do that?

New Post: Visual Studio 2012 Support

nazbrok — Fri, 14 Dec 2012 16:02:27 GMT

Hi,

Any ETA for the support of VS2012 ?

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.

New Post: VS2010/VS2012 and black background of 'Find results' window

firebie — Fri, 12 Oct 2012 10:08:13 GMT

Somehow VS ignores values of my foreground/background and always uses default colors for matched strings in find results window.

FindResultsFilename Foreground"=dword:0000ff00
FindResultsFilename Background"=dword:00000000

FindResultsSearchTerm Foreground"=dword:0000ff00
FindResultsSearchTerm Background"=dword:00000000

New Post: VS2010/VS2012 and black background of 'Find results' window

firebie — Thu, 11 Oct 2012 12:38:23 GMT

Great plugin!

Is it a bug of VS itself or plugin's?

I have a black background in 'Find results' window and, when plugin installed, for all results, that plugin hightlight in the window, used white background instead of black.

Plugin v1.4.5.

New Post: Visual Studio 2012 Support

konste — Tue, 09 Oct 2012 01:52:30 GMT

Are you planning to release an update for 2012 any soon?

And dear Onion, please, take it easy! No need to feel bad (or blue) only because Microsoft screwed here and there. It is not your fault and even not your problem. We do what we can to make it better and if something is broken beyond repair... oh well, we'll leave with it (or without it).

Konstantin

New Post: Visual Studio 2012 Support

blueonion — Tue, 09 Oct 2012 01:38:13 GMT

1. If the problem I reported has been fixed I should be able to resolve the issue with the restart.

2. Migrating VSColorOutput to use the 2012 SDK has been quite frustrating. I've only recently got it to migrate.

3. Yes it is more logical to put the colors in the Output Window category. Visual Studio does not support adding colors to this category. I've complained to Microsoft bitterly about this.

4. Some systems just behavior "weird" with regard to background colors. You'll have to set the background colors manually.

New Post: Visual Studio 2012 Support

konste — Sat, 06 Oct 2012 00:14:18 GMT

I use VSColorOutput with VS 2012 RTM and would like to note a few things here:

1. Changing colors still require VS restart, even for RTM version of VS 2012. Indeed seems to be a bug in VS. Oh well… At least it is not necessary to do it too often.

2. RTM version of VS SDK is definitely available since August: http://www.microsoft.com/en-us/download/details.aspx?id=30668 It would be great to have VSColorOutput officially updated for 2012.

3. I don’t understand why VSColorOutput colors are listed in Text Editor category. Would not it be logical to place them in the Output Window category?

4. Default settings for VSColorOutput colors look weird on default VS Output window. VS sets Output window background to light gray color and VSColorOutput uses white background by default. Could you please make them match?

Thank you for the great Add-in!

Konstantin

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.

New Post: Visual Studio 2012 Support

blueonion — Mon, 03 Sep 2012 12:48:53 GMT

The version in the Visual Studio Gallery should work. Changing colors will require exiting and restarting. This was due to a bug in VS that I'm told is fixed in the final release. When the production version of the Visual Studio SDK is released I'll update this plugin. Supporting the beta Visual Studio releases turned out to be a huge waste of my time. Lesson learned. Only support released versions.

New Post: Visual Studio 2012 Support

evakili — Sun, 02 Sep 2012 19:54:09 GMT

Dear VSColorOutput developers,

Is there any plan to support Visual Studio 2012?

Regards,

E. Vakili

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).

Created Release: Version 1.4.5 (Jul 04, 2012)

blueonion — Wed, 04 Jul 2012 17:33:33 GMT

New feature: Build Report Summary (credit goes to axxie). This in an opt-in feature so you'll have to enable it on the options page.