This is an old question, but in order to keep this resource valid: it’s true that you can add links like this, as Ross and Reed suggest, but I don’t think this is an actual solution, you are “just fixing the effect of the problem, not the reason "
Just as @dumbledad says, I received the same error message when I included files in my project that were marked as “Page” in the .csproj file, causing Visual Studio to compile this resource. However, it was an incompatible resource (in my case it was a XAML file, there could also be an image). Visual Studio requests additional assemblies. In this case, do not just add them, but go to your .csproj file and configure the following:
Find the opening node '<Page' and make sure that each instance of it is actually a page that needs to be handled by the appropriate action. In my case, as you can see, the resource is marked as the page that VS is trying to compile:
<ItemGroup> <Page Include="sitecore\shell\ClientBin\EmptySplashScreen.xaml"> <Generator>MSBuild:Compile</Generator> </Page> </ItemGroup>
Just delete this section (or Page-node) and return the file to the .csproj file as normal content. You must do this manually, since including a file from VS restores the same invalid Page-node. So I returned it to the project file as follows:
<Content Include="sitecore\shell\ClientBin\EmptySplashScreen.xaml" />
Et voila, your project will be built again, and the error message will disappear without the need to add these additional assembly links.
Rob habraken
source share