richardszalay
commented
6 years ago It turns out that this is actually already done by the regular publishing pipeline, but the project in question had so many warnings it wasn't seen.
Closed meduar closed 6 years ago
richardszalay
commented
6 years ago It turns out that this is actually already done by the regular publishing pipeline, but the project in question had so many warnings it wasn't seen.
When more than one project includes a content file with the same relative path, it's difficult to know which one will be deployed. It would be great if a warning was generated for any duplicates.