DiagnosticReport Throws System.NullReferenceException in PowerShell Core Beta 9 about easy.common

[NimaAra]

Thanks for reporting this. Here are some questions for you:

1. Is generating the report running on a NON .NET Core app on the same machine successful?
2. Can you try generating the report on the same machine but this time running on a .NET Core app?

Thanks.

[pldmgg]

Regarding 1) yes, the report works fine on the non .Net Core App (i.e. .Net Framework App) Windows PowerShell 5.1.

For 2), I can't actually load the .dll in the .Net Core App (i.e. PowerShell Core 6 beta 9), so I can't even attempt to generate a report. The error message when I try to load the netstandard2.0 .dll in PowerShell Core is in my original post. I think the stacktrace is pretty descriptive, but I haven't really done a deep dive into your code.

Let me know if you have any other questions. Thanks again for looking at this!

[NimaAra]

At this stage I am not at all interested in PowerShell, can you simply create a .NET Core Console application and try generating the report. I just did the same and had no problem generating a report.

The error which you have posted does not relate to loading the dll, the dll has been loaded but the generation of the report seems to have problems; My hunch is PowerShell Core perhaps does not support an API which I am using to generate the report. Hence my request to try this with a working .NET Core app rather than using PowerShell.

You should be able to create a .NET Core Console app and reference the NuGet package which will use the NetStandard2.0 dll.

[pldmgg]

You're right, about the dll loading. I wasn't thinking.

Creating a .Net Core Console App does, indeed, work.

Oh well, maybe I'll dig into Easy.Common.DiagnosticReport.<AddProcess> at some point and inspect further.

[NimaAra]

Yeah I suspected the problem would be coming from incomplete API in PowerShell Core. I am closing this for now as there is not much I can do but feel free to reopen once you have it investigated.

[NimaAra]

This should now be fixed in: v2.6.7. Please try again and report back if still a problem.