Bug: Installation of .NET requested although already installed

[pstein]

On my Win10 system I already installed in the past (64bit) .NET Desktop Runtime v8.0.13 (which includes .NET core v8.0.13).
I verified this.

Now when I start LogExpert v1.11.1 I got an error popup:

"You must install or update .NET to run this application"

LogExport seems not to recognize the the installed .NET.
This is a bug.

Pls verify

If ASP.NET Core Runtime 8.0.13 is required:
I prefer not to install it.
As far as I remember there was a LogExpert version in the past which did not require ASP.NET Core Runtime but only .NET Core
Which version number was the last with .NET Core only?

[Hirogen]

whats the reasoning behind not wanting to install asp.net core runtime?

Logexpert always support RPC calls between Logexpert instances, and with .net 8 and further, there is no native RPC support in winforms, that can be used. So there is the need to use something else, currently that is GRPC which is available with asp.net core.

I'm open to other RPC standards that can be used and don't need anything other then .net 8+

[RandallFlagg]

@Hirogen why is gRPC used for communication between the different instances? Why not other solutions such as "Named Pipes"?

[Hirogen]

grpc is the goto solution that even microsoft steers to, at least thats what in the docs. I'm open to simple solutions, but grpc provides a variety of options and opens logexpert to receive logging messages through other means then just opening a logfile.

Also it, was the first solution that poped up to replace the old win32 interprocess communication that was no longer supported since .net 6

but I'm open to other flexible options

[RandallFlagg]

grpc is the goto solution that even microsoft steers to, at least thats what in the docs. I'm open to simple solutions, but grpc provides a variety of options and opens logexpert to receive logging messages through other means then just opening a logfile.

Also it, was the first solution that poped up to replace the old win32 interprocess communication that was no longer supported since .net 6

but I'm open to other flexible options

I agree about the receive logging messages through other means part but I think that for the IPC part Named Pipes is a better solution. One can argure about why to do a few solutions(IPC, Differnt sources, etc.) but I think that we should choose the right tool for the problem.

[RandallFlagg]

Will be addressed in #374