Tag.NET

Hierarchical State Machine with Fluent Definition Syntax (.NET)

H

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 moved to Google Code

b

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

Agile UI Development in .NET: Nested Views

A

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)

C# Coding Style Guidelines

C

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:

Agile UI Development in .NET: Model Commands

A

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.

Agile UI Development in .NET: Presenter

A

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

Agile UI Development in .NET: UI Commands

A

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:

Agile UI Development in .NET: View

A

Last time we started looking at sample code with the view-model class for the UI to send messages on channels (table of contents). In this post, we continue with the next responsibility, the visualization. The View The view is responsible for visualizing the domain model to the user. We have seen in the last post that the view-model provides a simplified mini-model to the view. That means that the view does not have to care about the domain model as a whole with all its interactions and...

Agile UI Development in .NET: View-Model

A

After the posts (table of contents) in which I covered why we need an agile UI design pattern, it’s big picture and the needed tools, I start digging into sample code. I’ll show in each post a small part of the whole picture. If you want to get all at once then you find the source of all samples at . ProCollEE is my playground to experiment with WPF and UI design. Lets start Yes, let’s start. But where? There is one UI design pattern – presenter first (link) – that...

Agile UI Development in .NET: Tools

A

In the last post, I showed you the big picture of my UI design pattern. Before I can start showing you sample code for the different parts, I need to introduce some tools, which are used to glue all the tiny parts together:

Dependency Injection
Design By Contract
Synchronous and Asynchronous Communication
Test Driven Development

Recent Posts