0

I've the same question of How to have different Project Dependencies for each Project Configuration?, but the provided solution is very outdated and I'm not able to reproduce it on VS2017.

I'm receiving this error, and I don't know how to exclude the project from the linking.

Error CS0006 Metadata file 'path\to\my\excluded\library.dll' could not be found

tmm360
  • 404
  • 4
  • 13
  • Assuming you are using the new csproj format, Could you possibly provide the csproj file that has this problem? – Svek May 29 '17 at 17:10
  • Is a WPF project with .net framework 4.6.2, it has the old format – tmm360 May 29 '17 at 17:11
  • Does your solution use a combination of old libraries and new? (ie new csproj formats with old formats) – Svek May 29 '17 at 17:27
  • No, only old projects with .net framework 4.6.2. I've unchecked the build checkbox on the configuration manager for the unwanted project, and removed with pre-compilation conditions any reference on code. – tmm360 May 29 '17 at 17:39

1 Answers1

0

I've realized that the best way to perform this is to create a new root project with different dependencies, and choose by configuration which to compile.

tmm360
  • 404
  • 4
  • 13