Telemetry SecondMonitor (Timing & status App)

I've tried those things except installing in a different location, but now I did and didn't work.

Next thing I'll try when I get some free time is attempt to compile on the Release target and see what happens.

PS: It's strange because it really feels like Windows Defender or something else is blocking access to something, probably the Connectors folder, but when you look for evidence of it there's nothing. I should add that when I remove the Connectors folder from the installation the exact same thing happens, the program never gets to check for the folder it seems.

 

It's really weird. You could also try to copy the content of the 'Deployment' folder (that contains the fully build app) from the solution to the install location and see what happens. See if it works then.

 

Didn't work but...

I made some further experiments on Visual Studio and I think I'm now reproducing the error there, previously it wasn't happening because the plugin DLLs were not all there, the program ended with the "No plugins loaded" message but it did load the connectors as I mentioned.

So I figured we needed those plugin DLLs which I copied from the release installation, when I do that I'm getting an error exactly where it makes sense given the logs, after the plugins are loaded and before the connectors are loaded on the line:

var plugins = kernel.GetAll<ISecondMonitorPlugin>().ToList();

That function ends up with functions within functions and I ran out of time to pinpoint more exactly where it's crashing but the VS log I'm attaching is throwing a few System.IO.FileNotFoundException. Possibly within the .NET installation given that it's in the middle of loading other .NET DLLs.

 

This time I think it's fixed for good. Since that log was pointing towards .NET files not being found, I decided to uninstall every .NET, AspNetCore and Windows Desktop installation.

Then when opening SecondMonitor it pointed me towards what needed to be installed, precisely Windows Desktop 8.0.26 and AspNetCore 8.0.26 and it worked!

When trying to fix this problem I had installed Windows Desktop 8.0.26 already but not AspNetCore 8.0.26, maybe that would've fixed it earlier, can't know now.