I have some content files that I would like to share between a number of projects in Visual Studio.
I have put these files in their own project, set the build action to “Content”, and the copy to output directory to “Copy if newer”. I would like all these files to be copied to the bin/debug directory of the projects that reference them.
I can get it to work by including a reference to the “contents” project in each of the projects that need the files, but that requires that a minimal assembly be generated (3K). I assume there is a way, using MSBuild, to make this all work without creating the empty assembly?
Thanks to everone who took the time to make a suggestion about how to solve this problem.
It turns out that if I want my compiled content files to be treated like content files (in that they get copied to the output directory of any other project that references my project), I need to create a target which runs before GetCopyToOutputDirectoryItems, and add the full path of the compiled content files to the AllItemsFullPathWithTargetPath ItemGroup. MSBuild calls GetCopyToOutputDirectoryItems for projects on which the current project depends, and uses the resulting file list to determine the files that are copied along with the assembly.dll. Here is the XML from my .csproj, just in case someone else has a similar problem.
I have a custom task called “ZipDictionary”, and I accumulate all the files that I am going to compile in an ItemGroup called DictionaryCompile. My target, “FixGetCopyToOutputDirectoryItems” is executed before “GetCopyToOutputDirectoryItems”. I don’t do the actual compilation there, since this target can be called multiple times by referencing projects, and it would hurt performance. The target does some transforms to get the post-compilation file names, and then returns the full paths to all the files, since relative paths will not work when copy is called from the referencing project.