Use Case Assemblies

Introduction

In BPUA, a use case is not only a conceptual business unit. It is also a deployment and activation unit. The current platform code is designed so that use case functionality can be loaded from assemblies rather than compiled into the host as static knowledge.

Why Use Cases Are Separate Assemblies

This design supports several architectural goals:

What a Use Case Must Provide

A use case assembly is expected to follow the contracts and attributes defined by the platform. That includes transition handlers, state handlers, services, or page assemblies marked in ways the boot pipeline can discover.

The current contracts project already contains attributes such as:

Breadcrumbs and Use Case Location

In the activation code, the physical folder for a use case is resolved from either the identifier breadcrumbs or the use case name. This means the logical request path also participates in how the runtime locates the use-case payload.

Summary

Use case assemblies are the mechanism by which BPUA turns architectural independence into runtime independence. They let the platform host many future business units without hard-coding them into the host application itself.

Table of Content BPUA Chapter Previous: Transition Routing Next: Dynamic Assembly Loading

 

Business Process Programming in .Net
© 2004-2026 Laskarzhevsky Software Inc.
Unless otherwise noted, the content of this website is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
Code examples are provided under the MIT License.
You are free to share and adapt the material provided that appropriate credit is given and any modifications are clearly indicated.
The information provided on this website is for educational purposes only.
The author and publisher make no warranties regarding the completeness or suitability of the information and are not responsible for any damages resulting from its use.