Distributed Processing in Rider is empty

Hi Remco,

In Rider, the Distributed Processing window is empty, whereas in Visual Studio on the same machine, there are three nodes

Both NCrunch Versions are 5.12.0.10

Regards,
Sergei

Hi Sergei,

Thanks for sharing this. Could you clarify if the contents of the window are still rendering correctly? Is the entire window blank? Or do you just not see any nodes in the tree?

Hi Remco,

The window is rendered correctly. Only the nodes are missing.

Regards,
Sergei

Thanks Sergei. If you add a node via the toolbar options, does it appear in the list?

When I try to add an existing in VS Node, then i can see an Error Message "This server has already been added to the list of known servers".
When I try to add an new Node, then it doesn't appear in the list. But it appear in global config file.

Would you mind submitting a bug report when you have the distributed processing window open? I think something is bugging out when pulling data out of the backend.

Does the corner spinner popup indicate that the nodes are being used by the engine? It should be possible to see the extra capacity if the engine is connecting to them as normal.

Done

Thanks for sending through the bug report.

It looks like the issue is caused by a missing dependency on your machine. You'll need to install WMIC to resolve this problem.

Background: The grid management window uses this tool to obtain system information when it builds the window. The tool has previously been bundled with all versions of Windows, but MS decided that under Windows 11 its no longer there by default. I've noted this down for review.

Yes, that helped. Why can the VS plugin handle it on its own?

spolonski wrote:Yes, that helped. Why can the VS plugin handle it on its own?

This is because the Rider plugin is running the NCrunch engine process under .NET 6, where the VS plugin is using .NET Framework. The platform in this area behaves differently between these versions. NET6 couldn't provide a particular service, so we had to use a workaround. Now Windows has changed, so the workaround doesn't work anymore. So we need to find a new workaround :)