_From @zigzag312 on October 26, 2017 12:22_
Result: Content file will be copied to bin/Debug folder on build, but it will NOT be copied/deployed to bin/Debug/AppX folder.
I am using Visual Studio 2017 v15.4.1 on Windows 10 Fall Creators Update
_Copied from original issue: dotnet/project-system#2925_
Any info on this?
Having this same issue on a Xamarin UWP app. I have a .NET Standard library that contains a json file that I've specified as build action "Content" and "Copy if newer" or "Copy always". It never gets deployed! Is there a workaround for this?
I'm using VS2017 Enterprise and running Windows 10 Version 1803.
Workaround here would be to put the content file inside the UWP project or in a Shared Project which you will reference from your UWP project. Content files directly in the UWP app project will be deployed correctly. The problem here occurs only with content files in a separate library.
@MartinZikmund Oh boy, I really don't like that workaround. All of my content files are related only to the .NET Standard library project, not the UWP project that references it. I also use this .NET Standard project as a reference to a WPF project, and that setup works fine. I guess I'll have to duplicate a "copy" of each content file now into my UWP project.
Unfortunately it is the only workaround I have found so far...
Following hack worked for me: https://stackoverflow.com/questions/3610845/add-as-link-for-folders-in-visual-studio-projects
Far from perfect, but better than manually copying files to UWP project.
Most helpful comment
Any info on this?