Home

Cormo is a .NET application development framework that brings both Spring and the CDI (Contexts and Dependency Injection) spec from Java EE (specifically its implementation by [JBoss Weld] (http://weld.cdi-spec.org)) into .NET development.

Cormo's main objectives is Productivity.

• A simpler way for application components to interact. Traditional layered architecture is often rigidly bloated with vertical stacks of indirections that become heavy and unmanageable as your codebase grows. JavaEE 6 introduced CDI as the standard glue for independent parts of your application and eliminates several layers of indirections and abstractions, resulting in a more organic and pragmatic layering. It makes many common .NET patterns and "best-practices" superfluous (interfaces, repository, read/write services, commands, handlers, event-bus). Instead the magic words are YAGNI and KISS. (Read#1, Read#2)
• Remove ceremonies out of writing code. Cormo aims to provide an environment to develop and host modules that you can pick and plug onto your application to speed up development and take care of plumbing works so you don't have to. Writing code shouldn't be so hard: configuring IoC, ORM, auditing, security, messaging, events, logging, transactions, scheduling, health-monitoring, etc, I want to only need to say so and they just happen. Spring-Boot is a great framework that currently offers such capability, and Cormo tries to bring it to .NET environment.

Browse:

• Quickstart
• CDI Introduction
• Entity Framework
• Events and Observers
• Interceptors
• Scopes and Contexts
• Exception Handlers

Further Reading

The current state of Cormo's documentation is pretty sad. Well luckily the specs and frameworks that Cormo is based on come with great documentations. A lot in those documentations are applicable to Cormo (or what Cormo will come to be), so check them out. Just replace the word "Bean" with "Component".

• JBoss Weld [ Doc ]
• JBoss Seam 3 [ Doc ]
• Spring Framework [ Doc ]
• Spring Boot [ Doc ]
• JAX-RS [ Doc ]