Caliburn is an open-source client framework for WPF and Silverlight applications. Caliburn implements a variety of UI patterns for solving real-world problems. Patterns include MVC, MVP, Presentation Model (MVVM), Commands and Application Controller.
The key goals of Caliburn are:
- Support building WPF/SL application that are TDD friendly.
- Simplify various UI design patterns in WPF/SL.
- Simplify the use of a dependency injection container with WPF/SL.
- Simplify or provide alternatives to common WPF/SL related tasks.
- Provide solutions to common UI architecture problems.
Caliburn on CodePlex
ClientUI™ is a next-generation user interface library by Intersoft Solutions for the Silverlight and Windows Presentation Foundation (WPF) client platforms. ClientUI provides a full set of application fundamental libraries and an integrated architecture.
A ClientUI-family component shares the same ClientUI Framework and a set of common APIs, which enables developers to reuse the same code in both client platforms. Every ClientUI component works and behaves consistently on both platforms.
Download ClientUI
Introducing ClientUI
Ignition is an open-source WinForms framework designed for rapid application development. Instead of creating full-blown WinForms applications from scratch, Ignition serves as a framework that provides database access, reporting, scheduling, web service access, and one of the best interfaces in the WinForms world to help you get your application off the ground quickly. Ignition requires DevExpress.
Ignition on CodePlex
Introduction to Ignition
OXM is an open-source framework for transforming .NET objects to/from XML. Features include:
- Full control over the generated XML
- POCO approach, i.e. no attributes to pollute your domain entities
- Fluent DSL for defining the mapping
- Strongly-typed, which is good for refactoring
- No reflection
OXM on Google Code
nRoute is an open-source composite application framework for creating MVVM-style applications in Silverlight, WPF, and Windows Phone 7.
nRoute 0.4 is now available with many new features including:
- Multi-Platform Support – targets Silverlight, WPF, and Windows Phone 7
- Asynchronous Routing and Navigation
- Support for Globally Registered Navigation Containers
- “Stateful Browsing" Navigation Container
- Navigation Adapters
- Support for Error Pages, including custom Error Pages
- Support for MVC-style Controllers (replaces Url-based Actions)
nRoute on CodePlex
What’s New in nRoute 0.4
AutoPoco is an open-source framework for fluently building meaningful test data from Plain Old CLR Objects. AutoPoco replaces manually-written object mothers and test data builders with a fluent interface, providing an easy way to generate lots of test data in a short time.
AutoPoco on CodePlex
PostSharp is the leading aspect-oriented programming (AOP) framework on the Microsoft .NET platform. With PostSharp, you can easily write and apply custom attributes that add new behaviors to your code — tracing, thread management, exception handling, data binding and more.
PostSharp was created in 2004 as an open-source project and was serving its first commercial customers by mid-2005. Eventually it became clear that the open-source model would not provide the resources necessary to properly support the project. Customers wanted a reliable support team, so the commercial company SharpCrafters was created. The result is a new commercial version of the product: PostSharp 2.0.
SharpCrafters Website
MEF Contrib is a community-developed library of extensions to the Managed Extensibility Framework (MEF). MEF Contrib will enable you to:
- Share custom tools
- Design and discuss ideas for new parts/modules
- Find tools and parts/modules for your project
- Connect with others on MEF development
MEF Contrib
MEF on CodePlex
The Managed Extensibility Framework (MEF) simplifies the creation of extensible applications. MEF offers discovery and composition capabilities that you can leverage to load application extensions.
MEF presents a simple solution for the runtime extensibility problem. Until now, any application that wanted to support a plugin model needed to create its own infrastructure from scratch. Those plugins would often be application-specific and could not be reused across multiple implementations.
[More]
