WPF (Windows Presentation Foundation) 의 현재와 미래

WPF 에 대해 전반적인 이해와 기술동향을 찾아보던 중 궁금중을 말끔하게(?) 도와준 블로그를 찾아 보관해본다.

http://10rem.net/blog/2010/10/28/the-present-and-future-of-wpf

일부내용..

Our Guidance

Speaking of guidance, I'm often asked for guidance with how to choose between WPF and Silverlight. Here's what we recommend when starting a new application:

• If you're just starting out, and there's a question as to which technology to choose (Silverlight or WPF) then start with Silverlight. It is generally easier to move up to WPF from Silverlight than it is to move the other way. Silverlight has a smaller API, and is therefore generally considered easier to learn.
• If you need a desktop application with only basic system integration, consider building a Silverlight Out-of-Browser application. Silverlight 4 Trusted Applications with IDispatch support provide access to many system resources previously unavailable to web technologies.
• If you need deep system integration, excellent multi-touch support, device access, local resources, and all the other things that go with a solid desktop application, then consider moving up to WPF.
• If you're a C++ developer, you can choose to go with C++ and MFC, or use C++ with WPF on the front end, like the Expression team did.

No matter what you chose (WPF, Silverlight, Native), rest assured that you'll be supported in the years to come with enhanced capabilities and our awesome programming tools.