Confused about XAML (How does it fit with Framework 2.0, ASP and Smart Client?)


Based on an article posted at C-Sharp Corner   - Several people have approached me with the following similar questions. (Please note the answers in green


Does this mean that WinFX will have its own Data access, IO, Security, etc. classes in its framework?
WinFX is the .NET Framework 2.0 plus WPF (Windows Presentation Foundation), WCF (Windows Communication Foundation) and WF (Workflor Foundation). So everything that developers know from .NET still applies, just that we've added some extra classes. All the things mentioned in this question are just core functions from .NET, and none are superseded or replaced as a result of WinFX.


Since WinFX will include XAML, which from what I understand can be used to write both windows and web apps, then how does Asp.Net fit into WinFX (if at all)?  What will be the guidelines  used when developing a web app to determine if XAML or Asp.Net should be used (besides the client OS being XP-SP2 or greater)?  One person told me that you won't have to choose - whatever the heck that meant!
Windows Presentation Foundation uses XAML for constructing user interfaces, certainly. And you can use WPF to build applications that run in a standalone window or in-browser, that's true. But both classes of applications are smart client applications, that is to say that they both require the WinFX Runtime to operate. The browser application model in WPF allows for really rich, dynamic, visually immersive applications to be deployed via the web, but it's not HTML. ASP.NET is still our server technology for building HTML apps.


I've seen the comments on the list about "Atlas forever changing the way web apps are implemented", how does Atlas fit into the whole WinFX picture?
Atlas is an extension to ASP.NET that makes it easier to build AJAX applications. It enables web applications to become more dynamic - loading data without requiring a complete page refresh, for instance. It's something that we'll ship as part of "Orcas". It's a good step for a web application, although it doesn't approach the richness of WPF (Windows Presentation Foundation)


Can you confirm Microsoft’s commitment to providing WPF plug-ins for alternative browsers?


As we communicated last year, we are creating a portable version of WPF that will target alternative browsers and O/S in addition to Windows. It is called “WPF/e”. WPF/e bridges between server based web programming and client programming. We will discuss this some more at MIX next week.


 


Is MS committing to both AJAX (Atlas) and WPF concurrently?


Atlas capabilities can get you limited fidelity of user experience (UE). WPF/e and furthermore WPF and WINFX can provide a better/best experience for customers everywhere and on Windows.


 


And if both WPF and Atlas are the future, what criteria does Microsoft expect customers to use when choosing one of the two products?


We expect applications that have an important UE part to rely on WPF (on Windows XP and Vista) and WPF/e (Everywhere) while applications that can compromise on UE will use Atlas or even less than that pure ASP.NET (html rendering). XAML is the new way to define compelling UI and WPF/e and WPF are the way to tie the UI to an application.Also, in terms of complexity of the code on the client, Atlas is limited while WPF/e and furthermore WPF are more capable and can use managed code on the client.


 


Skip to main content