But if you've already got a captive audience able to run anything .NET 4.0 and above (incl. async/await via Bcl.Async libraries) with the rich experience of WPF, why bother shoehorning a web application as a solution?
Our users are in a manufacturing environment, on a well-known environment. It's practically like developing for a gaming console. And in that light, WPF seems to be a good fit.
I have pretty limited experience with desktop stuff (mostly Winforms) but with the SPA frameworks now it's about as expressive and deployment issues go away (which is nice in a small shop where you can't just foist them on someone else).
Comments
Perhaps. I am not familiar with the project.
But if you've already got a captive audience able to run anything .NET 4.0 and above (incl. async/await via Bcl.Async libraries) with the rich experience of WPF, why bother shoehorning a web application as a solution?
Our users are in a manufacturing environment, on a well-known environment. It's practically like developing for a gaming console. And in that light, WPF seems to be a good fit.
I have pretty limited experience with desktop stuff (mostly Winforms) but with the SPA frameworks now it's about as expressive and deployment issues go away (which is nice in a small shop where you can't just foist them on someone else).