viacheslav-lozinskyi / metaoutput Goto Github PK

View Code? Open in Web Editor NEW

46.0 46.0 7.0 29.76 MB

Work with output data / log files never been so simple!

C++ 72.53% C# 25.15% Batchfile 2.33%

metaoutput's People

Contributors

Stargazers

Watchers

Forkers

erisonliang tomasz-stochmal carlosmachina kingdistributionsincorporated luisllamasbinaburo dano7

metaoutput's Issues

Xaml Hot Reload for Xamarin.Forms fails to start on Android devices in VS2019 (16.11.1)

If you try to debug a Xamarin.Forms project deployed to an Android device or emulator the Xaml Hot Reload will fail to start with the following error. I initially commented on the bug reported here https://developercommunity.visualstudio.com/t/xaml-hot-reload-encountered-a-problem-and-failed-t-14/1503640 but I was able to solve the issue by disabling the MetaOutput extension. I'm not sure there is a problem with the extension it could very well be an issue with visual studio.

[4:41:33 PM]  XAML Hot Reload initializing...
[4:41:35 PM]  Caught exception in AgentStatusChangedHandler at 313: System.NullReferenceException: Failed to obtain Mono Debugger Evaluation Context.
   at Xamarin.HotReload.DebuggerExtensions.GetEvaluationContext(SoftDebuggerSession debugger) in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\DebuggerExtensions.cs:line 33
   at Xamarin.HotReload.HotReloadBridge.<InitializeAgent>d__47.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 123
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.HotReload.HotReloadBridge.<<Debugger_TargetHitBreakpoint>b__50_0>d.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 262
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
   at Xamarin.HotReload.DebuggerExtensions.GetEvaluationContext(SoftDebuggerSession debugger) in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\DebuggerExtensions.cs:line 33
   at Xamarin.HotReload.HotReloadBridge.<InitializeAgent>d__47.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 123
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.HotReload.HotReloadBridge.<<Debugger_TargetHitBreakpoint>b__50_0>d.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 262
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
[4:41:35 PM]  XAML Hot Reload encountered a problem and failed to start. Use Help -> Report a Problem if the issues persists.
[4:41:35 PM]  Stopping All Hot Reload sessions due to Failed ...
[4:41:35 PM]  (TestApp3.Android) Stopping a Hot Reload session due to Failed ...
[4:41:35 PM]  Stopped Hot Reload session.
[4:41:35 PM]  (TestApp3.Android) Caught exception in Debugger_TargetHitBreakpoint at 266: System.NullReferenceException: Failed to obtain Mono Debugger Evaluation Context.
   at Xamarin.HotReload.DebuggerExtensions.GetEvaluationContext(SoftDebuggerSession debugger) in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\DebuggerExtensions.cs:line 33
   at Xamarin.HotReload.HotReloadBridge.<InitializeAgent>d__47.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 123
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.HotReload.HotReloadBridge.<<Debugger_TargetHitBreakpoint>b__50_0>d.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 262
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
   at Xamarin.HotReload.DebuggerExtensions.GetEvaluationContext(SoftDebuggerSession debugger) in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\DebuggerExtensions.cs:line 33
   at Xamarin.HotReload.HotReloadBridge.<InitializeAgent>d__47.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 123
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.HotReload.HotReloadBridge.<<Debugger_TargetHitBreakpoint>b__50_0>d.MoveNext() in D:\a\1\s\HotReload\Source\Xamarin.HotReload.Bridge\HotReloadBridge.cs:line 262
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

Allow previewing of variables from 'Locals' or 'Autos' while in Debugging

Imagine I am debugging and I have a NewtonSoft JObject variable. Those can be so hard to view in the 'Locals' or 'Variables' debug menu. Can I view this JObject using MetaOutput? It would be so great!

For instance, when viewing a JObject in Debug, it's really hard to see the properties because they're all nested in various layers of .Jobject and .JToken.

Imagine a simple JSON payload like this one, for an ARM Deployment.

#testfile.json

{
	"location": "eastus2",
	"tags": {
		"key9183": "aa"
	},
	"properties": {
		"publisher": "Microsoft.Azure.Security",
		"type": "IaaSAntimalware",
		"typeHandlerVersion": "1.3",
		"autoUpgradeMinorVersion": true,
		"settings": {
			"RealTimeProtectionEnabled": true,
			"ScheduledScanSettings": {
				"IsEnabled": true,
				"ScanType": "Quick",
				"Day": 7,
				"Time": 120
			},
			"Exclusions": {
				"Extensions": "",
				"Paths": "",
				"Processes": ""
			}
		}
	}
}

When this is loaded as a JObject, it becomes a nightmare to read in the debug context.

var o1 = JObject.Parse(File.ReadAllText(@"c:/Temp/testfile.json"));

It gets squished into one line, and there is no 'Previewer' to view it as JSON.

If I expand the properties to look at it, the JObject becomes a very deeply nested object in the Debug window.

⬆️ - became a very deeply nested object even though it is simple JSON.

It would be excellent to be able to view a JObject or JToken right in MetaOutput and see it as JSON.

Add a setting to select the default mode or memorize the last setting

Hi, I have an improvement idea.

MetaOutput should provide us a setting to define which mode should be the default and select it automatically when build/debugging/etc. starts and ends.

The current behavior is to reset the mode to "Content highlight mode". For example if I prefer "Filter mode" I must switch to it manually every time. In addition, switching modes clears the filter expression end I have to set it back again manually.

My suggestion is to add sub-menu "Default mode" to "Settings" with the following elements:

Filter mode
Content highlight mode
Comment highlight mode
Console mode
You could use "checkable" menu items to indicate the current setting.

=== OR ===

A simpler approach could be memorizing the last mode and don't switch over to another automatically.

Also the filter expression (the text in the input box next to the mode switch buttons) should be retained.

text to audio

I like to use text to audio but unfortunately only "Test run finished" is converted. Need to know if passed or failed.

Dump build output verbose?

Hello, would like to ask if with your extension is possible to dump the output window build verbose.

I'm trying to find a way to detect when a build fails and then perform an action, see:
https://stackoverflow.com/questions/74022549/run-a-visual-studio-event-on-build-failure

Is it possible to increase MetaOutput font sizes?

How can I change the background color of MetaOutput window ?

Thanks for this great extension.
I use MetaOutput with VS2022.
I'd like to change the background color of MetaOutput window (dark red color in the screenshot below) , but I'm not sure what element of color should be changed.
Can I change the color by using Environment - Fonts and Colors configuration in VS2022 Options ?

Ability to step through previously typed text

A common console/terminal feature is being able to using the [up-arrow] and [down-arrow] keys to step through previously typed text. The proposed implementation or other method (drop-down menu e.g) for selecting previously typed text would greatly improve the productivity.

Thank you for creating such a great software.

Application crash if the extension is enabled

I've stumble on this extension yesterday and it seems great.

My application crash at random location if the extension is enabled. As soon as I disable the extension I can launch/debug my application again.
At first I though it was some new code I wrote, but after commenting/reverting the application would still crash.

Any idea?

Icons should be at the top like screenshot below

Option to change fonts?

Hi, i would really appreciate a way to modify the font for MetaOutput. Take a look at this screenshot to see why:

MetaOutput window continues to report DirectX warnings after debuggee has been stopped.

Hello. When I debug a DearImGUI application and get a message from the DirectX subsystem then the MetaOutput gets stuck and the endless following messages appear:
D3D12 : ID3D12CommandList::DrawIndexedInstanced: Viewport: 0 is non-empty while the corresponding scissor rectangle is empty. Nothing will be written to the render target when this viewport is selected. In D3D12, scissor testing is always enabled. [ EXECUTION WARNING #695: DRAW_EMPTY_SCISSOR_RECTANGLE] @@@source DEBUG @@@type WARNING

The time in the left corner of the Debug.Begin upper line ticks, “Program started” slider in the right corner runs but the program has been already stopped indeed and the standard VS Output window reads “The program XXX hax exited with code 0 (0x0.”
Closing or clearing MetaOutput window does not help and I need to restart the Visual Studio to continue to work. Starting a next debugging session does not help.
I do admit it may be a Visual Studio problem but I cannot tell for sure – I am DearImGUI and DirectX newbie.
P.S. The same messages appear in the standard Output window but they stop to appear when the debuggee is stopped.

C++ Support

Clicking the 'eye' icon to go to the source of the issue doesn't work in C++
Sometimes the error is 'collapsed' so you have to click the '+' to see it.

need to be able to copy text message to clipboard

right-click and have Copy option on popup menu?