Thursday, August 25, 2022
Our team have recently been working on a project to migrate the existing Sitecore MVP site, to run against XM Cloud. One part of this involved upgrading the version of the Rendering Host, which was previously built using ASP.NET Core 3.1 to the latest version - .NET6.
The upgrade path was a simple process and allowed us to leverage a lot of the new framework’s features, like the new Minimal Hosting Model. However, we did run into one small issue, the project was originally built following the Sitecore Helix standards which involved splitting different pieces of functionality into separate projects. This worked fine when running the application in Docker or directly from within Visual Studio, but I started getting a new error when I tried to publish the project…
Error NETSDK1152: Found multiple publish output files with the same relative path: C:\Solutions\XM-Cloud-Introduction\src\Feature\BasicContent\rendering\Views\_ViewImports.cshtml, C:\Solutions\XM-Cloud-Introduction\src\Feature\Navigation\rendering\Views\_ViewImports.cshtml, C:\Solutions\XM-Cloud-Introduction\src\Feature\Social\rendering\Views\_ViewImports.cshtml, C:\Solutions\XM-Cloud-Introduction\src\Feature\User\rendering\Views\_ViewImports.cshtml.
This was indicating there was an issue with each referenced project containing its own _ViewImports.cshtml file. This wasn’t an issue when building the app using .NET Core 3.1, so something must have changed with the migration to .NET 6.
A bit of googling led me to this document from Microsoft that confirmed this was a feature included in .NET 6 to stop duplicate files being included in publish artifacts.
So how do we get around it, well it turns out it’s fairly simple. All we need to do is to add the following line to our Rendering Hosts project file and then everything worked again!