.runsettings
does not support deployment items the same way as with .testsettings
unfortunately, and I for one find this very frustrating as it was a very clean way of deploying dependencies. There is a setting related to it in .runsettings
(DeploymentEnabled
), but all this seems to control is running tests in a separate directory, rather than the application's output directory.
After much trial and error, I ended up just changing all the .csproj
files in my test projects to have a CopyIfNewer
build action in the Properties window in Visual Studio so that all the dependencies would be copied into the output folder so they'd be found when running the tests.
I think all told I spent about 2-3 hours updating all the tests to get them running again.
On the plus side, things run a lot faster now as there's no need to copy all the binaries to a new directory after they are compiled, as everything runs "in-place".