I just released Ninject 2.2.1.0 and Ninject.MVC3 2.2.1.0. Both are bugfix releases. In this Blogpost I’ll explain if you have to update and what changes you need to do in case you are using th NuGet version of Ninject.MVC3.
Updated: new version here! I have compiled two cheat sheets about clean code (the ones mentioned in my post about Code Quality!). The first covers clean code – code that is easy readable and keeps changeable. The second is about Test Driven Development. Both cheat sheets list principles, patterns, practices and smells. You can download them here – Clean Code Cheat Sheet V1.3, Clean TDD Cheat Sheet V1.2. Take a look! I’d like to read your feedback in the comments section… (just an...
I’m going to speak about code quality (see my short version of the presentation) at the conference BASTA! BASTA! is mainly focused on .NET technology and gives you the opportunity to see and speak with a wide range of technology experts. If you have any feedback of what you are missing in my short presentation, please write a comment here or on the post with the presentation. The short version takes about 30 minutes and my speak at BASTA! is scheduled for 1 hour and 15 minutes. I will...
The .NET component library bbv.Common (open source – Apache License 2.0) provides a powerful hierarchical state machine. Its features are: value type based (enums, ints, …) resulting in single class state machines. actions on transitions entry and exit actions (parametrizable) transaction guards hierarchical different history behaviours to initialize state always to same state or last active state fluent definition interface synchronous/asynchronous state machine passive state...
bbv.Common – a .NET library containing components for
(a)synchronous loosly coupled event notifications (event broker),
hierarchical state machines,
active objects and asynchronous workers to build robust multi-threaded applications,
context based loosely coupled rule engines
and much more
has move from sourceforge.net to Google Code.
Check out the project at
Join the discussion at
Updated: Something went wrong with the code snippets. Now it’s okay.
Today, we”l have a look at nested views in my series on agile UI development in .NET using an extended MVVM pattern (table of contents).
There are two kinds of nested views:
contextually nested views and
hierarchically nested views (master-detail scenarios)
In the last couple of weeks, I ran over some posts about c# coding style guidelines, i.e. guidelines about how to arrange (style) your code. This normally includes things like where to put paranthesis, how fields are named (e.g. with/without _) and so on.
All these posts (no I don’t have the links anymore) had two things in common:
In my series on agile UI development in .NET, we have seen quite a lot so far (table of contents). But up to now, we never made a call to the model (business logic, services and so on). This is the topic of this post: Model Commands.
A Model Command encapsulates a single action hat is execute against the model. This can be a query to request data, an action that modifies data, communication with a completely different part of the system or anything else your application has to do on the model.
Next in my series (table of contents) on agile UI development in .NET is the presenter. The presenter is responsible to drive the UI workflow. This means that the presenter is the control center to react to:
events from the model. For example that data has changed.
events from embedded presenters
calls from parent presenter
calls from UI commands
In this post, we are going to have a look at UI commands. UI commands are responsible for reacting to user input, for example the send button click in the sample I use throughout this series of agile user interface development in .NET series. For other posts in this series look here: table of contents.
We have seen in the last post that the view binds a command to the send button that it gets from the view-model: