This project is read-only.

Namespace and folder structure

The attached picture presents a sample project folder structure.
Components, commands and messages on the picture are grouped into subfolders, but storing them in a single namespace would be better.
Therefore the Login use case should be placed in a dedicated subfolder. Its content should be as follows:
  • LoginComponent
  • LoginRequestMessage
  • LoginResponseMessage
  • LoginCommand
  • LoginCommandArgument
  • LoginCommandResult
The folder Services contains all global providers, managers, handlers, persistors. These classes could be instantianted as additional properties of your custom ComponentContainer or added to its components collection and referenced using its First<>(), FirstOrDefault<>() or Many<>() methods.

Note that the folder structure of the main project is recreated also in the test project. It simplifies navigating through the folder structure.

Recommended folder structure in the Solution Explorer

Last edited Jan 23, 2013 at 6:13 AM by polo, version 3


No comments yet.