#1 - They shouldnt hold off on releasing the non LH ones until LH time, its only hurting them and hteyre developers.
An interim release of the framework is coming early next year. It will include version 2.0 of C#, ASP.NET, and additions to pretty much every other part of the framework.
Will the 2004 release of the runtime get these non LH classes?
Well, there are a lot of "non LH classes"... so I guess it depends on what you mean. Do you mean everything except for Avalon/Aero? If so, no. Most of that stuff isn't even close to done.
As for XAML, well thats all well and nice until we all end up as web dev whores for even the simplest application.
I think you're giving XAML a bad wrap. If you don't care about UI/Code seperation, application development will be no different. You'll drag/drop stuff onto your form, and off you go. The beauty of XAML is that you have the option of that seperation.
Will it be possible to prevent users from changing my UI if I use XAML? If it doesnt, I refuse to support XAML.
The XAML can be compiled directly into your application so it can't be modified.
|