WinAppCLI should use project's nuget.config file when present

[chiaramooney]

Is your feature request related to a problem? Please describe.
In ADO projects can't use the public nuget feed, they need to create a custom and use a feed to be able to install nuget dependencies. They typically specify that custom feed via a nuget.config file.

winappcli currently doesn't check if a project has specified a nuget.config file, so when npx winapp restore is run winappcli always uses the public nuget feed even when I project has specified a custom feed in a nuget.config file.

Describe the solution you'd like
Expose a way in winappcli for a project's nuget.config file to be used by winappcli during nuget install steps. Ideally winappcli would assume the file (if present) is in the current directory where npx winapp restore is being called. Otherwise, the dev could specify where the file is like npx winapp restore --config path/to/config.

Additional context
Note temporarily you can get this to work by copying your nuget.config file into .winapp/packages and then running restore.

[JesseCol]

Note temporarily you can get this to work by copying your nuget.config file into .winapp/packages and then running restore.
Interesting -- that seems hacky, but does it unblock you for now?

I see we call "nuget install" in NugetService.cs. Looks like that accepts a -ConfigFile arg we could use. Or, we could have the winapp.yaml specify the feed source URL, and call "nuget install" with the -Source parameter.

[nmetulev]

Note temporarily you can get this to work by copying your nuget.config file into .winapp/packages and then running restore.
Interesting -- that seems hacky, but does it unblock you for now?

I see we call "nuget install" in NugetService.cs. Looks like that accepts a -ConfigFile arg we could use. Or, we could have the winapp.yaml specify the feed source URL, and call "nuget install" with the -Source parameter.

I like both options, maybe we can support both.

I'm a bit unsure about automatically picking up a nuget.config however as not sure if that is always the desired behavior - should we require the user be specific about using a different config/source?

[azchohfi]

Since we are just calling nuget.exe, I would use the defaults from nuget.exe. It will make it easier for developers to understand our tool (It just works). We are calling nuget.exe but we are not honoring its defaults, so we should always use the config file if it is in the same path as the one that nuget.exe would look at.