.NET Core 3.1 Worker Service - Publish with environment variables not working as expected

I am trying to publish a .NET Core 3.1 Worker Service app using different publish profiles.
I have setup 2 publish profiles, one for Development and one for Production, with very similar settings for both:
```

Development
FileSystem
Release
x64
netcoreapp3.1
D:\Workspace\Tools Publish\Worker
win-x64
true
False
False
False

```
The only difference between the two profiles is the **EnvironmentName** element, which is set to **Development** and **Production**, respectively.

However, setting this element seems to have no effect on the actual output of the publish operation, as starting the app that was published using the **Development** profile (via .exe) will result in the app running under the **Production** hosting environment.

Can anyone help? Am I experiencing some weird issue or is this indeed broken right now?

Note: I am using Visual Studio 2019, I don't know if the IDE could be causing this

(P.S. I have also published some ASP.NET Core 2.1 apps previously and for them the **EnvironmentName** element worked correctly, the publishes producing apps with different configurations depending on the publish profile used)