Mustrum_Ridcully
Legend
Working .NET 3.0 at this moment, I am not convinced that WPF 3D is fast enough for an application like the Virtual Gaming Table. DirectX programming be more effective (even if WPF is actually relying on DirectX in the end, it still seems to have a very costly abstraction layer)Plane Sailing said:True, I was thinking about when it was submitted as a standard in 2000.
Arguably if they are looking for Windows development experience the big issue I would expect to see noted would be the version of .Net framework they want people to have experience with, since using C# (or whatever) against .Net 1.1, .Net 2.0 or .Net 3.0/3.5 will result in very different implementations simply because of the capabilities of the framework.
I'm guessing that they are not using .Net 3+ because of the desire for DirectX experience, but considering that .Net 3.0 apps can run on WinXP sp2 and Vista PCs, that must cover pretty much all of their target (wintel) market... and I'd bet that they could do pretty much everything within XAML and .Net 3.0 that they think they need DirectX for.
Cheers
I love working with .NET and dread the days (that will probably come, as my current project in my company might end in the forseeable future...) where I have to programm with C++ again. But .NET 3 and WPF are still not perfect for 3D applications. (But I would take WPF over Winforms or Java swing & co every time when designing a GUI.)