4 ms·
A product I worked on was a victim of Microsoft changing preferred APIs. Their competing product which the prior year had less market share somehow sported the
by babesh 10y ago
A product I worked on was a victim of Microsoft changing preferred APIs. Their competing product which the prior year had less market share somehow sported the new UI instantly when the UI became publicly available. Monopolistic behavior if you ask me.
- regularfry 10y agoIt's why I got out of the MS ecosystem. I bought quite heavily into WPF for the Vista launch, and it was obvious that was a dead end within a couple of years. Not only that, but I could see exactly the same thing happening to all the other neat stuff I was planning to look into at the same time. That was not the way to encourage my long-term membership of the Visual Studio clan.
- pjmlp 10y agoWPF is alive and doing pretty well. Doing new WPF application development for the last three years for the biotech industry. It is also the official API for classical desktop application and shares a lot with UWP.
- flukus 10y ago> and it was obvious that was a dead end within a couple of years As the other reply probably indicated, it's still not apparent to .net developers. MS really dropped the ball with providing a clear path for desktop development.
- regularfry 10y agoI was specifically doing 3D stuff in WPF. That end of things didn't get much love after the initial release (or if it did, it came too late for me).
- douche 10y agoHow were you doing it? It's definitely possible to embed DirectX in a WPF control, and not particularly hard to do, with SlimDX or SharpDX, in my experience.
- regularfry 10y agoDeclarative 3D data in XAML, not touching DirectX directly at all. Viewport3D at the root, then doing the right magic to get the sort order of the objects right (working around the built-in logic, in other words).