Error handling is different for compiled bindings about maui HOT 4 OPEN

I've updated the description to point to my repo. If you run the UnitTests in Debug configuration, they will fail because a NullReferenceException is thrown. If you run the UnitTests in Release configuration they will fail because the exception will be swallowed and no BindingError will be logged.

from maui.

Verified this issue with Visual Studio 17.10 Preview 5 (8.0.21). Can not repro issue with sample project.

from maui.

I have updated the repo to .21 (sorry, didn't check this before - kinda assumed that dotnet new will create a project using the most recent version). Strangely I also had to adjust the test and add yet another mock... but anyway, the issue is still there.

BTW, I am not running this in Visual Studio but from the command-line:

dotnet test -c Debug
[xUnit.net 00:00:00.28] UnitTests.Issue22078Tests.SetBindingContext [FAIL] Failed UnitTests.Issue22078Tests.SetBindingContext [189 ms] Error Message: System.NullReferenceException : Object reference not set to an instance of an object. Stack Trace: at MauiIssues.Issue22078ViewModel.get_ObjectType()

vs

dotnet test -c Release
[xUnit.net 00:00:00.26] UnitTests.Issue22078Tests.SetBindingContext [FAIL] Failed UnitTests.Issue22078Tests.SetBindingContext [176 ms] Error Message: If a binding throws an exception, I kinda expect diagnostic logging :) Stack Trace: at UnitTests.Issue22078Tests.SetBindingContext()

from maui.

Thanks for your explanation, executing from the command line can reproduce the issue.

from maui.