Duplicate process exception thrown for non-dapr processes

[ante-maric]

Expected Behavior

If I have FortiClient VPN running, which happens to have Windows Service running as scheduler.exe process, I should be able to use dapr scheduler.

Actual Behavior

When FortiClient VPN is running and I want to use dapr scheduler InvalidOperationException is thrown with message "Process {existingProcess.Name} PID:{existingProcess.Id} is already running with duplicate settings. Dapr does not permit duplicate equivalent instances on a single host." should not be thrown.

Steps to Reproduce the Problem

1. Find any exe file, rename it to scheduler.exe and run it
2. Try to use dapr sidekick in your app with scheduler

This should be easy to fix. ProcessFinder should take into account path where dapr processes are located, not just process name which do not necessarily identify process we are looking for.

At the moment there is a workaround, although not very nice one. You can rename scheduler from dapr to dapr-scheduler.exe and change ProcessName of DaprSidekick settings in appsettings.json to match.

Release Note

RELEASE NOTE: