- VS error message when closing VS during a debugging session
- VS can now do multiple debugging session in a row without needing restart. Issues:
- Unhandled exceptions in DataReceived event handler caused UpPipe to break resulting in total loss of connection between AD7Process and ToolsWindows
- Added new code to clean out the Action handler that PipeServer uses. By holding onto the old Action reference, it was holding onto a reference to the old AD7Process instance thus reulting in all sorts of weird errors.
- VS crashes completely without VIX API - now just shows error message in Output window.
- Colours of text in Cosmos windows invisble in dark theme. Tenp fix: Bg colour forced to light,
- XSharo project referencing outdated libraries.
Slowly fixing the debugger...
- Single-level fields now work.
- "This" in locals window now works - this and #1 were related to SQLite issue that was just a bad line of code
- Arguments/Stack window now displays correct values. Used to display same value for both args and stack mistakenly.
Locals window now works! (For primitive types and pointers only.) Exceptions related to unrecognised (i.e. more complex) types should be caught and display as the local variable's value instead of causing VS to crash.
Autos window still causes instant VS crash.
Cosmos windows works.
Call Stack works (sort of...only ever displays current line)
Threads works (but there is only ever 1 thread so not very helpful)
Watch window is only capable of doing 1 watch result per break - step to next line to be able to run another - will look into why this is.
This is relatively stable but no to be considered complete. Currently supported:
1. Installing user/dev kit (as normal)
2. Creating C#/VB/F# projects (latter 2 untested)
3. Debugging a Cosmos project - see limitations list below.
Debugging limitations:
1. Breakpoints sometimes fail to be hit. Only known thing that may help is recompile everything.
2. Specific breakpoint failure case: If you try and place a breakpoint on or after a "while(true)" statement it is extremely unreliable.
Other limitations:
1. VMWare occasionally breaks. If you get "Internal error" messages, or if VS crashes (don't let Windows "fix" it) or if VMWare fails to load properly there is only one known & reliable solution: Re-run the VMWare installer and hit "Repair". No restart required. You won't lose your VMs or settings (AFAI can tell).
If it all breaks, feel free to rant at it ;)
