cache-dependency-path does not support list of file names, but in description it's said, thay it can about setup-dotnet

[priya-kinthali]

Hello @Denyyyys 👋,
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

[suyashgaonkar]

Hi @Denyyyys, we did had look into this and we see that cache-dependency-path does not accept multiple paths in a array. You can try by passing multiple paths with help of pipe operator, that should hopefully resolve your issue. Please let us know incase you still face the issue. Please find a small example below for your reference.
with:
dotnet-version: 8.0.x
cache-dependency-path: |
'./appsettings.Development.json'
'./appsettings.json'

[Denyyyys]

Hello @suyashgaonkar.

Thank you for your response!

Unfortunatelly, your solution didn't work for me. When I use the same configuration as you showed, it implicitly sets cache: false, which means the cache is not used. In this case, everything works as expected, but I want to use the cache. When I try to add cache: true and use the pipe operator like this:
dotnet-version: 8.x
cache: true
cache-dependency-path: |
'./backend/WebServer'
'./tetBackend'

I see the following error: Error: Some specified paths were not resolved, unable to cache dependencies. You can see my job logs for this configuration using that link. My repository in that state is available under this link, so feel free to use this repo.

Even if you figure out how to use the cache with package.lock.json files from ./testBackend and ./backend/WebServer paths, the build pipeline fails during the test phase.

Any help you can provide would be greatly appreciated!

[suyashgaonkar]

Hi @Denyyyys , the way cache dependency works is that builds and restore the cache depending on the changes found in packages.lock.json file, hence we need to pass the absoloute path to the package.lock.json file in the cache-dependency-path.You can check the official documentation on the same in the following url: https://github.com/actions/setup-dotnet?tab=readme-ov-file#caching-nuget-packages.
We did fork your repo to work upon the issue and attached screenshot has the result with suggested solution.

Another alternative that we can suggest to help you with caching dependecy is actions/cache Github action. You can find detailed documentation and examples related to caching in the follwing links :
https://github.com/actions/cache
https://github.com/actions/cache/blob/main/examples.md#c---nuget