Paul Davis

Results 18 comments of Paul Davis

I have the same issue in MudBlazor 5.2.4. If I make any async method call in the same event as my _dialogService.Show(...) then I get: ``` crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception...

Thanks, I do on my production projects

Coverage tab: ![image](https://github.com/FortuneN/FineCodeCoverage/assets/96231736/cd4d9d03-dd4e-4f74-8c1b-945cc48a19d1) Coverage Log: ![image](https://github.com/FortuneN/FineCodeCoverage/assets/96231736/0cb045f5-1ac6-4be3-b227-4609fd9f805a) No, I'm not using MS Code Coverage

FCC output: https://pastebin.com/0JQeeqiC But if I remove the package, my test library works. So how is it MAUI?

Created a repo to demonstrate: https://github.com/pauldavis-dwe/FccBugRepro.git

I thought for a moment that worked, but no. It DOES now show coverage for the UnitTests project but not for the Core project: ![image](https://github.com/FortuneN/FineCodeCoverage/assets/96231736/5a31a336-1c27-4590-8d69-55702702d5b8)

The Cobertura.xml file now has lots more in it for the Dwellant.ResidentApp.Core.UnitTests "package" but nothing for Dwellant.ResidentApp.Core which is the assembly I am testing

> I have installed the Maui components and run coverage on your https://github.com/pauldavis-dwe/FccBugRepro.git With the package reference and RunMsCodeCoverage Yes code coverage is collected. I just tried that and I...

> But can you still show the FCC Output Window Pane output just for the MS Code Coverage Run. Sure: https://pastebin.com/Mq3UbiEF

Have tried the coverlet suggestion but still no coverage