dotnet user-secrets --project option does not support relative paths

[natemcmaster]

From @dougbu on May 12, 2016 17:13

1. It isn't clear why we need the --project option at all. The dotnet user-secrets command must be executed in a project directory with Microsoft.Extensions.SecretManager.Tools fully configured.
2. If this option is needed, it should support relative paths. That would at least be useful in corner cases where user secrets are used in a group of projects but only one has the tool configured.
3. dotnet user-secrets list --project $pwd/../../src/UserSecrets.work is ugly as sin.
4. What is the parameter named root?

For example

dotnet user-secrets list --project ../../src/UserSecrets.work

Results in

critical: Command failed : The path must be absolute.
Parameter name: root

Copied from original issue: aspnet/UserSecrets#77