This Site Has Moved!

Due to CodePlex shutting down, this site has moved. For the latest and greatest about CODE Framework, beyond the information and versions provided here, check out After October 1st, 2017, no updates will be added to CodePlex. Instead, this project will be maintained on the aforementioned site.

CODE Framework Documentation


We are in the process of writing a whole series of Articles which will be published in CODE Magazine. Check out the Articles page for more information.

Quick Tips

We are in the process of compiling a list of "quick tips" (most of which are excerpts from internal EPS/CODE emails) which will all be published in the Quick Tips page.

Articles and Whitepapers

Building WPF MVVM/MVC Applications

Building Middle Tiers

Change Logs


For further information and documentation on the CODE Framework, see

Quick Introduction to using the Framework

The easiest way to get started with the CODE Framework, is to install the CODE Framework Tools Visual Studio Extension through the Visual Studio Extension Manager:


Once these extensions are installed, new project templates become available in Visual Studio, such as these:


Note that this does not install the actual framework, but only the tools. However, if you use a template that requires framework components (such as the CODE Framework WPF MVVM/MVC template), the tools detect the dependency and show a dialog like this:


Using this dialog, CODE Framework assemblies can be added to the current project, either by adding files stored locally in a folder or ZIP file (after having downloaded the desired version manually from CodePlex), or you can let the tool retrieve the latest version from CodePlex for you and add the assemblies directly.

Note that CODE Framework assemblies are generally not installed in the GAC (although you could do so yourself if you prefer this option) but they are put into a dummy location in the local solution. This has the advantage that different solutions built with the CODE Framework can use different versions without colliding with each other, and allowing the developer full control over when and to what version a certain solution is to be upgraded to. It also has the advantage that all external assemblies can be checked into source control, allowing other developers to simply join the project through source control without relying on additional installs. This also allows them to always retrieve the correct version of these dependencies automatically. This generally works very well for typical business applications.

Last edited Sep 30 at 4:41 PM by MarkusEgger, version 20


No comments yet.