3 ms·
I was in a similar situation, having an idea for a desktop app, and I dove straight into .NET / WPF on Windows. My reasons were that a) there are great many Wi
by teekay 13y ago
I was in a similar situation, having an idea for a desktop app, and I dove straight into .NET / WPF on Windows.
My reasons were that a) there are great many Windows computers around and people still use them, b) .NET and WPF are mature and documentation is available on MSDN / StackOverflow.
With Windows 8 around, however, I am also looking at WinRT and will most likely dabble in that, too.
- dgellow 13y agoAnd now, what do you think about that choice? Do you only target windows users? Are there some drawbacks you can warn me about? I have done C# development but only on server side.
- teekay 13y agoI would love to be able to support Linux and Mac but am not willing to dig into C++ / Qt or similar alternatives. It's a hobby project, which I should have mentioned previously, not a commercial work. C# is great and WPF/XAML is OK; I can't really make any profound comments as I've only done web development previously and am not familiar with any other desktop technologies. With regards to HTML5/Javascript superseding WPF in the future, I am not convinced - Microsoft should shed some light on their plans in the near future (the Build conference is in April I think) so we'll see.