This project is read-only.

Why do we need this?

Topics: Developer Forum, Project Management Forum, User Forum
Mar 23, 2007 at 12:02 AM
Hi Kent, Good work. But it seems to be not useful. See this article link:

As he stated in this article, CAB architecture provides a way to develop 3.0 worksapces without any wrappers.
Mar 24, 2007 at 9:12 AM
Edited Mar 24, 2007 at 9:13 AM

I have posted questions against the article. Awaiting feedback...

Apr 25, 2007 at 12:03 AM
Uh.... I find Kent's WPF CAB extremely useful. It's actually what the CAB guys had in mind when they developed "Microsoft.Practices.CompositeUI.WinForms.dll"

CAB was developed in a UI toolkit agnostic way so that they could support WPF in this very way. Swap out the Winforms.dll for a WPF one and you've got a smart client framework for WPF.

Sure you can do interop between winforms and wpf like you are doing but that isn't what my project requires....we wanted a native WPF application and the wpfcab layer is the only native solution we've got.

Thanks Kent!