Thanks for the new installer! A few issues:
Bug: To access the resources in 'AppResources.resw', the ResourceLoader needs to be constructed like this: new ResourceLoader("AppResources"). Should be a simple fix. new ResourceLoader() always looks for 'Resources.resw' in the running app, even
if it is missing.
Installer: Not a big deal at all, but I had to uninstall the old version before I could install the new version.
Windows Store apps definitely prefer the name 'Resources.resw'. 'ms-resource:StringName' always looks there, though I think you can redirect with 'ms-resource:///AppResources/StringName'.
There's probably no way to redirect the XAML resources (e.g. 'MyButtonId.Content') so I'll probably just stick with Resources.resw and use this to avoid naming conflicts: using AppResources = My.Namespace.Resources;
The best "documentation" is buried in this sample: http://code.msdn.microsoft.com/windowsapps/Application-resources-and-cd0c6eaa. Changing that sample to use your code generator might be a good way to test the different scenarios.
It looks like a resw file in a class library would have to be additionally qualified with the assembly name, e.g. new ResourceLoader("AssemblyName/ResourcesName"). I'm not sure how you'd support that with the code generator.