The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
2021-05-09 02:04:00(UTC) at Lat:41.6, Long:350.7 - North Atlantic, just off Portugal
Margin of error? Um. Errr ... eh .... trivial, really ... +/- 60 minutes
So, that's pretty much anywhere within an 18,000 mile radius of Portugal then ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
Windows Forms succeeded Visual Basic 6 in 2002, just as WPF succeeded Windows Forms in 2006. WPF brought with it XAML: a declarative language for UI. Microsoft developers had never seen anything like XAML. Today, Xamarin and UWP bring XAML to iOS, Android, HoloLens, Surface Hub, Xbox, IoT and the modern desktop. In fact, XAML is now the technology building the Windows OS itself.
Developers around the world love XAML because it’s so productive and flexible. Microsoft engineers feel the same; we’re building our own apps and even Windows 10 with XAML. The future is bright, the tooling is powerful and the technology is more approachable than ever.
Understandable, I've started a few apps in WPF and gave up in desperation but I kept at it and am slowly learning...slowly! The hardest part for me has been the binding, it is so powerful but binding problems can sometimes be like chasing pointer problems.
I found building dynamic UI in Winforms was a lot easier than WPF; I built an industrial control UI interface that let the end user build their own screens for what they wanted to look at. Winforms let you use GDI+ for making custom graphics or controls, WPF took that away, and had you layer other shapes and items to a new control (annoying). WinUI gave us back the ability with Win2D NuGet package for DirectX drawing and was decent.
I worked with WPF for a couple years, and put out some big projects with it at my last job, but I just could never "like" it, after I left that place, I told myself never to work with it again.
I feel if WPF had been close to standard HTML5/CSS3 it would have been a home run. MS could have had their own "React native" type framework before React took off, and be able to bring in web UI designers into a familiar syntax.