CobaltFusion / DebugViewPP

DebugView++, collects, views, filters your application logs, and highlights information that is important to you!
Boost Software License 1.0
1k stars 143 forks source link

Add visual studio build output as message source #262

Open codenotes opened 7 years ago

codenotes commented 7 years ago

It would be terrific if we could direct the output of Build to DebugView. For large projects, it can be just so difficult to find the errors among a stream of warnings, boost complaints, etc. DebugView would be a powerful tool to help find what's meaningful in the build output.

You already have a forwarder VSIX, would it be tough to plug into the debug output in visual studio?

janwilmans commented 7 years ago

it is easy, to try it, just change GUID_BuildOutputWindowPane in Forwarder.cs to GUID_BuildOutputWindowPane

However, to put it into production code, I would need to make an options window to choose to enabled/disable this. And currently I'm working on the CTimeLine class

So, feel free to try it and if you could add an option window to the .vsix I would gladly accept a pull request...

The way to create an options page is described here: https://msdn.microsoft.com/en-us/library/bb166195.aspx

with options comes the need for persistence:

public static WritableSettingsStore GetWritableSettingsStore(this SVsServiceProvider vsServiceProvider)
{
    var shellSettingsManager = new ShellSettingsManager(vsServiceProvider);
    return shellSettingsManager.GetWritableSettingsStore(SettingsScope.UserSettings);
}

MSDN: WritableSettingsStore