Are there any best practices for building XAML for use in a custom C++ app? As far as I can tell right now, the requirement is to copy your resources to a folder relative to the BuildTool, and then copy the output back into the application. Would it be possible to allow specifying input/output paths when running Resource.BuildTool to make building XAML assets in-place more straight-forward?

Also, have you guys thought about opening up the API used in the BuildTool command line app? Maybe for embedding the XAML export processing into an existing asset build pipeline?

Hi Matt,

Are there any best practices for building XAML for use in a custom C++ app? As far as I can tell right now, the requirement is to copy your resources to a folder relative to the BuildTool, and then copy the output back into the application. Would it be possible to allow specifying input/output paths when running Resource.BuildTool to make building XAML assets in-place more straight-forward?

With the current version you have to copy your resources inside Data/Packages directory. The output (cache) is generated at /Bin/Data/. This cache can be later wherever you want if you implement a custom filesystem for your application (viewtopic.php?f=3&t=313).

This is one of the changes we are preparing for v1.2. We are aware that the current system is very restrictive and intrusive. Having to copy things inside the SDK is not a good idea.

Also, have you guys thought about opening up the API used in the BuildTool command line app? Maybe for embedding the XAML export processing into an existing asset build pipeline?

That is the way it is done. BuildTool is a wrapper for the interface IResourceDbSystem. You can interact with that system in the same way that BuildTool does.