09.10.2020 NuGet package update 1.6.12
- Fixed few livesharp.dashboard.cs issues
- Fix for `Binding … property not found` issue (https://github.com/OYIon/LiveSharp/issues/89)
livesharp.configfile is discontinued
LiveSharp.dashboard.csadded to your project. This file contains configuration for LiveSharp as well as easy access to the LiveSharp Runtime.
LiveSharp.dashboard.cseven if you are not in debugging mode. Make sure to use
LIVESHARP_DISABLEcompilation symbol to remove LiveSharp from deployment builds.
Buildmethod to your user controls and pages it will automatically be called on every update.
livesharp.configruntime section. Set this option to
trueto disable CSS hot reload in Blazor
ReflectionTypeLoadException.Typesare loaded if the exception occurs during initialization
Trace.WriteLineoutput without attaching to the process
tryin async methods bug
??bug that occurred in certain cases
livesharp.configMore info here: https://www.livesharp.net/help/
ICommandproperties to the VM in runtime
baseconstructor call issue
Invalid ILissue for generic methods
forloop is now properly displayed in the debugger (https://www.youtube.com/watch?v=xwpRqD8DThw)
Server application has a proper debugger interface now. It can be found under the Inspector tab. Add the method you want to debug and see full execution flow when the method is invoked.
NuGet package fixes CustomRenderer support that was broken on Xamarin iOS and Xamarin UWP (possibly on some other platforms as well).
Live debugging is finally here for LiveSharp! Make sure to update both the LiveSharp Server Application and the NuGet package. Then, after connecting to the app, head to Inspector tab, and add a method you want to debug. You will see a list of invocations with parameter values. Clicking on an invocation will show you the whole execution flow with all the values.
Please head to https://gitter.im/LiveSharp/Lobby and tell me what works and what needs to be improved. I really appreciate your feedback!