When using Visual Studio 2017 to build UWP applications any Asset files that I mark with a Build Action of "Content" and set "Copy Always" for the "Copy to Output directory" property are getting copied to the projects appropriate \Bin ..\Debug project folder.
But those files are not getting copied over to the runtime Local\Packages .. \LocalState folder and therefore are not available to the app if I try to read them from the ApplicationData.Current.LocalFolder.
Is this a bug in Visual Studio or with my dev environment? Or is this by design? If it is by design, what is the recommended way of distributing a folder full of assets or data files with your app that you can enumerate through at runtime?
In the past, I have used the
StorageFile file = await StorageFile.GetFileFromApplicationUriAsync(new System.Uri("ms-appx:///assets/xxx.png"));
syntax when needing access to a specific file or two, but am looking for a way to deploy a folder of files that could contain 1-to-many files, depending on the purpose of the build and would rather not have to hardcode a long list of file uri's into the app for each file, and then alter it when changing out the files for a special build.