mrlacey
commented
6 years ago @bvillersjr Having looked at WAF I believe it's equivalent to what WTS would consider a 3rd party framework. The big difference it has from the ones we support at the moment (MVVMLight, Prism, and Caliburn.Micro) is that it ships entirely as source code, rather than via a compiled assembly.
Treating WAF as a framework in the WTS sense, we have plans to support an extensibility model so that any 3rd party framework can be included. From a WTS perspective, we're only able to support a small number of frameworks "in the box" because of the extra overhead that each one adds. This limits us to directly supporting only the most widely used ones.
The UWP version of WAF is also still in an alpha stage (and has been for over 2 years) so I'd encourage waiting for it to get to a stable/release level before doing any integration with it due ot the risk of rework as it makes changes.
We don't yet have a timeline for providing framework extensibility, however, if you think there specific things it does that you think we could include sooner please let us know.
Firstly, I would like to commend those involved with this project! This is a MUCH needed tool!
I would also like to suggest taking a look at the Win App Framework here (https://github.com/jbe2277/waf) and noting the MANY lightweight conveniences that it provides. What this project lacks, it has and what it lacks, this project has. Married, or at least partially married, Template Studio could transition from a convenient beginners framework to something very valuable to a beginners and intermediate level devs alike in my humble opinion.
I would list the features of WAF that I would like to see in Template Studio, but it would require writing a lengthy article. I hope the powers that be here will give it a serious look, if for no other reason than to gather ideas and see how others are solving similar problems.