Dapr run with file failing to connect to scheduler on Windows

[antontroshin]

Expected Behavior

Using Workflows .NET quickstart https://github.com/dapr/quickstarts/tree/master/workflows/csharp/sdk

When using dapr run -f . in WIndows, it should connect to the scheduler using the correct port :6060 (which differs from linux/macos default scheduler port :50006)

time="2025-03-04T20:51:07.5626908-06:00" level=info msg="Attempting to connect to scheduler: localhost:6060" app_id=order-processor instance=LAPTOP scope=dapr.runtime.scheduler type=log ver=1.15.2

Actual Behavior

When using dapr run -f . fails to connect to the scheduler, using incorrect port :50006 instead of :6060

time="2025-03-04T14:17:40.5233635+01:00" level=info msg="Attempting to connect to scheduler: localhost:50006" app_id=order-processor instance=LAPTOP scope=dapr.runtime.scheduler type=log ver=1.15.2
time="2025-03-04T14:17:40.524412+01:00" level=error msg="Failed to connect to scheduler host: failed to watch scheduler hosts: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp [::1]:50006: connectex: No connection could be made because the target machine actively refused it.\"" app_id=order-processor instance=LAPTOP scope=dapr.runtime.scheduler type=log ver=1.15.2

When using standard dapr run -- dotnet run from order-processor folder, everything works as expected.

Steps to Reproduce the Problem

1. Clone repo https://github.com/dapr/quickstarts/tree/master/workflows/csharp/sdk
2. Navigate to directory workflows/csharp/sdk
3. Follow the README.md instructions
4. Run dapr run -f .

Release Note

RELEASE NOTE: FIX Dapr run with file failing to connect to scheduler on Windows