Source: https://fireflyframework.org/frameworks/dotnet/
Language: en

netfly, the .NET framework by Firefly

# An application layer for ASP.NET Core, one module at a time.

netfly’s modules authorize commands, cache queries, publish to Kafka or RabbitMQ, and run sagas and try-confirm-cancel steps, with Polly policies and JWT security. Event sourcing is optional.

[Read the documentation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/e3bcb1eb4a2a77551a8c16414e6a61f5a14b5a33/docs/README.md) [View the source](https://github.com/fireflyframework/fireflyframework-dotnet)

1. 01 Service composition
2. 02 Domain boundaries
3. 03 Business operations
4. 04 History and projections
5. 05 External integrations
6. 06 Business coordination
7. 07 Identity and resilience
8. 08 Service operations

.NET 10 · C# · ASP.NET Core

Native stack and framework

## What netfly adds to ASP.NET Core and EF Core.

ASP.NET Core hosts and routes the service, and EF Core persists its data. netfly’s starters register its modules through the host’s dependency injection, and the data layer stays your team’s.

### Service composition

One of four starters registers a service’s modules for it.

With ASP.NET Core and EF Core alone, your team builds

Matching registrations in ASP.NET Core hosting, dependency injection, middleware, and configuration.

netfly provides

Core, Data, Domain, and Application starters that register module sets.

How it works

`AddFireflyCore` registers web, observability, cache, events, and CQRS. `AddFireflyApplication` adds resilience, security, actuator, scheduling, sessions, i18n, AOP, and WebSockets.

The starters leave out identity providers, orchestration, and rule engines. Register the ones your service uses.

[Core starter modules](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Starter.Core/FireflyCoreExtensions.cs#L32-L45) [Config server endpoints](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.ConfigServer/ConfigServerEndpoints.cs#L46-L109)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Starter.Application/FireflyApplicationExtensions.cs#L33-L63)

### Domain boundaries

Services code against netfly’s `IRepository` contract and keep their own EF Core configuration. Event-sourced ones also use its `AggregateRoot`.

With ASP.NET Core and EF Core alone, your team builds

Repository contracts and event-sourced aggregate conventions around your EF Core models.

netfly provides

Repository and filtering contracts and an event-sourced aggregate base. Your team writes the EF Core repositories.

How it works

`IRepository` defines find, save, delete, count, and paged queries. `AggregateRoot` applies changes, replays history, and tracks uncommitted events.

Your application registers its own `DbContext`, since the data starter registers none.

[Data starter without a DbContext](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Starter.Data/FireflyDataExtensions.cs#L22-L39) [Event-sourced aggregate base](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Domain/AggregateRoot.cs#L24-L63) [EF Core event store](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Store/EfCore/EfCoreEventStore.cs#L34-L50)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Data/Repository/IRepository.cs#L23-L31)

### Business operations

Commands and queries are checked before their handlers, and cached results clear on the events you choose.

With ASP.NET Core and EF Core alone, your team builds

Validation, permission checks, query caching, and invalidation around every command and query handler.

netfly provides

Command and query buses with authorization and query caching, plus attribute rules for cache invalidation.

How it works

`DefaultQueryBus` authorizes a query, then serves a cacheable result from the cache or stores the handler’s answer. `EventDrivenCacheInvalidator` clears the cache patterns that `[InvalidateCacheOn]` names.

Your application delivers events to the cache invalidator.

[Query authorization and caching](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Cqrs/Buses/DefaultQueryBus.cs#L38-L91) [Event-driven cache invalidation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Cqrs/Cache/EventDrivenCacheInvalidator.cs#L48-L90) [Handler registration](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Cqrs/DependencyInjection/FireflyCqrsExtensions.cs#L30-L60)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Cqrs/Buses/DefaultCommandBus.cs#L34-L68)

### History and projections

An event-sourced service writes its events once and builds delivery and read models from them.

With ASP.NET Core and EF Core alone, your team builds

Event versions, atomic event and outbox writes, a relay, and projection checkpoints.

netfly provides

An EF Core event store with an outbox, an outbox relay, snapshots, and a projection runner.

How it works

`ProjectionRunner` applies upcasters and projections from each checkpoint, and an EF Core store keeps snapshots. The relay and projections are hosted services.

The domain starter uses an in-memory event store, and the checkpoint store is in memory too.

[Outbox relay](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Outbox/EventOutboxProcessor.cs#L69-L96) [Projection runner](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Projection/ProjectionService.cs#L60-L113) [Event store and snapshot tests](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/tests/FireflyFramework.Tests/EfCoreEventStoreTests.cs#L36-L87)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Store/EfCore/EfCoreEventStore.cs#L40-L93)

### External integrations

Events go out through `IEventPublisher` to Kafka, RabbitMQ, or an in-process channel.

With ASP.NET Core and EF Core alone, your team builds

Kafka, RabbitMQ, and vendor SDK calls behind your own contracts and outbound policies.

netfly provides

Kafka and RabbitMQ publishers and consumers, a resilient publisher, and SendGrid and S3 adapters.

How it works

`ResilientEventPublisher` wraps any publisher in Polly retry, circuit-breaker, and timeout policies. The Kafka publisher enables idempotent production and waits for all replicas.

Publishers and consumers are configured separately: the Kafka publisher leaves the in-memory consumer in place.

[Kafka consumer](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Eda/Consumer/KafkaEventConsumer.cs#L50-L125) [RabbitMQ publisher](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Eda/Publisher/RabbitMqEventPublisher.cs#L52-L79) [Resilient publisher](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Eda/Publisher/ResilientEventPublisher.cs#L34-L67) [SendGrid provider](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Notifications.SendGrid/SendGridEmailProvider.cs#L34-L79) [S3 document storage](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Ecm.Storage.Aws/S3DocumentContentAdapter.cs#L35-L97)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Eda/Publisher/KafkaEventPublisher.cs#L32-L65)

### Business coordination

A recovery service finds stale runs of the saga, workflow, and try-confirm-cancel engines.

With ASP.NET Core and EF Core alone, your team builds

Step ordering, compensation, participant coordination, and recovery in your own hosted services.

netfly provides

Saga, workflow, and TCC engines, with a recovery service that finds stale executions.

How it works

`TccEngine` runs every Try, then confirms. A failed Try cancels the participants already tried. `WorkflowEngine` runs ordered steps with timers and signals.

The provided execution store is in memory. Supply your own for runs that must survive a restart. A failed TCC confirmation is recorded, not rolled back.

[Saga compensation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Orchestration/Saga/SagaEngine.cs#L100-L125) [TCC engine](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Orchestration/Tcc/TccEngine.cs#L33-L94) [Workflow engine](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Orchestration/Workflow/WorkflowEngine.cs#L44-L106) [Stale execution recovery](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Orchestration/Recovery/RecoveryService.cs#L59-L83)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Orchestration/Saga/SagaEngine.cs#L34-L75)

### Identity and resilience

Your code reads the request’s user and tenant from a security context and runs calls through named Polly pipelines.

With ASP.NET Core and EF Core alone, your team builds

JwtBearer settings, identity-provider clients, and Polly policies, kept aligned.

netfly provides

JWT bearer configuration, a security-context holder, identity adapters, and named Polly policies.

How it works

`AddFireflySecurity` configures ASP.NET Core’s JwtBearer authentication from Firefly options. `AddFireflyResilience` builds named retry, breaker, rate-limit, bulkhead, and timeout pipelines.

Validate the tenant at a trusted boundary: `SecurityContextMiddleware` takes `X-Tenant-Id` straight from the request.

[Named resilience registry](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Resilience/DependencyInjection/FireflyResilienceExtensions.cs#L20-L34) [Polly pipeline factory](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Resilience/Core/ResiliencePipelineFactory.cs#L22-L70) [Keycloak adapter](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Idp.Keycloak/KeycloakIdpAdapter.cs#L56-L84)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Security/DependencyInjection/FireflySecurityExtensions.cs#L32-L89)

### Service operations

Core services export OTLP telemetry. The Application starter adds actuator endpoints, and the admin client can register the service with an admin server.

With ASP.NET Core and EF Core alone, your team builds

Exporter setup, health and management endpoints, and a registry your services report to.

netfly provides

Firefly meters and runtime metrics, and an admin client that sends heartbeats and unregisters on shutdown.

How it works

Observability registers Firefly meters and sources, runtime metrics, and OTLP exporters. `AdminClientHostedService` registers the service, sends heartbeats, and unregisters on shutdown.

netfly doesn’t instrument HTTP or database calls. Secure the actuator endpoints yourself.

[Actuator endpoints](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Actuator/DependencyInjection/FireflyActuatorExtensions.cs#L20-L39) [Admin client registration](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Admin/Client/AdminClientHostedService.cs#L33-L69)

[See the implementation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Observability/DependencyInjection/FireflyObservabilityExtensions.cs#L26-L56)

Already in the native stack

ASP.NET Core provides hosting, dependency injection, routing, authorization policies, error handling, and caching. EF Core provides persistence and database transactions.

Your team still owns

Validation and authorization rules, command handlers, domain behavior, persistence, and the execution context. The data starter expects your own `DbContext`, and the Orders sample uses an in-memory repository.

Stored events

## An aggregate’s stored events feed a relay and your projections.

An aggregate’s events and their outbox rows commit together.

### How EfCoreEventStore commits an aggregate’s events

1. Your aggregate produces domain events.
2. `EfCoreEventStore` checks the version and writes event and outbox rows in one transaction.

#### Deliver committed events

1. The outbox holds unsent rows.
2. A hosted relay publishes them through the event publisher.
3. A sent row is marked afterward, so consumers must tolerate redelivery.

#### Build read models

1. Projection runners read stored events from their checkpoints.
2. Upcasters and your projections process each event.
3. The checkpoint store records each projection’s progress.

Ordinary repository writes don’t reach the outbox. Only `EfCoreEventStore` writes there.

[Event and outbox append](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Store/EfCore/EfCoreEventStore.cs#L40-L93) [Outbox relay batch](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Outbox/EventOutboxProcessor.cs#L69-L96) [Stored-event projections and checkpoints](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.EventSourcing/Projection/ProjectionService.cs#L60-L113)

Capabilities

## Pick the modules your service needs.

netfly / Conceptual architecture

The error middleware wraps command dispatch, and sagas, caching, and events are separate modules.

1. [01Validated command dispatch](https://fireflyframework.org/frameworks/dotnet/#dotnet-capability-0)
2. [02Attribute-based sagas](https://fireflyframework.org/frameworks/dotnet/#dotnet-capability-1)
3. [03Structured HTTP errors](https://fireflyframework.org/frameworks/dotnet/#dotnet-capability-2)
4. [04In-process caching](https://fireflyframework.org/frameworks/dotnet/#dotnet-capability-3)
5. [05In-process event delivery](https://fireflyframework.org/frameworks/dotnet/#dotnet-capability-4)

Amber: Firefly modules · Ivory lines: APIs · Amber lines: events

### Validated command dispatch

The command bus runs each command’s validation and authorization, then resolves and invokes its registered handler.

[See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Cqrs/Buses/DefaultCommandBus.cs#L34-L68)

### Attribute-based sagas

`SagaEngine` orders `[SagaStep]` methods by their dependencies. When a step fails, it calls the completed steps’ compensation methods in reverse.

[See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Orchestration/Saga/SagaEngine.cs#L34-L125)

### Structured HTTP errors

The error middleware turns exceptions into problem responses with a status, an error code, a trace id, and a correlation id.

[See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Web/Middleware/GlobalExceptionHandlerMiddleware.cs#L62-L116)

### In-process caching

The memory cache adapter reads, writes, and evicts values, including every key under a prefix.

[See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Cache/Adapters/MemoryCacheAdapter.cs#L47-L115)

### In-process event delivery

The in-memory publisher writes event envelopes to a channel per destination, and consumers read them in the same process.

[See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Eda/Publisher/InMemoryEventPublisher.cs#L24-L52)

Code

## Load an order with a netfly query handler.

`GetOrderHandler` takes its repository as a primary-constructor parameter and loads an order by id. It maps the order to an `OrderDto`, or returns `null` when none exists.

### Follow an order through the sample

1. #### Register the modules

   `AddFireflyCore` registers web, observability, cache, events, and CQRS, then the sample adds its repository.

   [See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/samples/FireflyFramework.Samples.OrdersService.Web/Program.cs#L23-L37)
2. #### Send a command

   The `POST /api/v1/orders` endpoint sends a `PlaceOrderCommand` through the command bus, with a demo user and tenant.

   [See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/samples/FireflyFramework.Samples.OrdersService.Web/Program.cs#L23-L44)
3. #### Test the dispatch

   The bus tests send a command to its handler and expect a validation failure for an empty one.

   [See the source](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/tests/FireflyFramework.Tests/CqrsTests.cs#L43-L67)

GetOrderHandler.cs

```csharp
using FireflyFramework.Cqrs.Queries;
using FireflyFramework.Samples.OrdersService.Core.Mappers;
using FireflyFramework.Samples.OrdersService.Interfaces.Dtos.V1;
using FireflyFramework.Samples.OrdersService.Models.Repositories;
using ExecutionContext = FireflyFramework.Cqrs.Context.ExecutionContext;

namespace FireflyFramework.Samples.OrdersService.Core.Services.Orders.V1;

public sealed class GetOrderHandler(IOrderRepository repository) : IQueryHandler<GetOrderQuery, OrderDto?>
{
    public async Task<OrderDto?> HandleAsync(GetOrderQuery query, ExecutionContext context, CancellationToken ct = default)
    {
        var entity = await repository.GetAsync(query.OrderId, ct).ConfigureAwait(false);
        return entity?.ToDto();
    }
}
```

[View the full file](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/samples/FireflyFramework.Samples.OrdersService.Core/Services/Orders/V1/GetOrderHandler.cs#L15-L30)

### Checks that run before the handler

`DefaultCommandBus` runs the command’s validation, then its authorization, and throws before resolving any handler. Both hooks allow everything until your commands define the rules.

DefaultCommandBus.cs

```csharp
        var validation = await command.ValidateAsync(ct).ConfigureAwait(false);
        if (!validation.IsValid)
        {
            throw new CqrsValidationException("Command validation failed", validation.Failures);
        }

        var auth = await command.AuthorizeAsync(context, ct).ConfigureAwait(false);
        if (!auth.IsAllowed)
        {
            throw new CqrsAuthorizationException(
                string.Join("; ", auth.Errors.Select(e => $"{e.Code}: {e.Message}")), auth.Errors);
        }
```

[View the full file](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Cqrs/Buses/DefaultCommandBus.cs#L43-L54)

Setup

## Build netfly from its source workspace.

Register your command assemblies and the starters you need in a .NET 10 application. Because the buses are singletons, scope each handler’s `DbContext` deliberately.

netfly has no public release tag. CI built, tested, and packed the pinned commit.

The error middleware maps CQRS validation and authorization failures to HTTP 500. Map them to 400 and 403 in your host.

[Read the documentation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/e3bcb1eb4a2a77551a8c16414e6a61f5a14b5a33/docs/README.md)

### The cache and events run in-process by default

Before you run several instances, configure the Redis cache adapter and a Kafka or RabbitMQ adapter.

[Read the migration guide](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/docs/MIGRATION-GUIDE.md)

Related

## The Orders sample and the framework’s saga and error tests.

### Orders service sample

The sample’s web, core, models, interfaces, and SDK projects.

[View the source](https://github.com/fireflyframework/fireflyframework-dotnet/tree/a41278325edd462a3fbcda096dd6cc44e48e908f/samples)

### Saga tests

Saga steps run in dependency order, and completed steps are compensated after a failure.

[Read the tests](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/tests/FireflyFramework.Tests/SagaTests.cs#L78-L96)

### Error middleware tests

Tests that check business errors become 422, timeouts 504, and web validation errors 400.

[Read the tests](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/tests/FireflyFramework.Tests/WebMiddlewareTests.cs#L47-L79)

Sources behind this page

- [Runtime configuration](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/global.json#L1-L7)
- [Starter module integration test](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/tests/FireflyFramework.Tests/StarterApplicationWiringTests.cs#L59-L80)
- [Exception translation order](https://github.com/fireflyframework/fireflyframework-dotnet/blob/a41278325edd462a3fbcda096dd6cc44e48e908f/src/FireflyFramework.Web/Middleware/GlobalExceptionHandlerMiddleware.cs#L70-L83)
- [ASP.NET Core native dependency injection](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-10.0)
- [EF Core native data lifecycle](https://learn.microsoft.com/en-us/ef/core/dbcontext-configuration/)
- [Build, test, and pack CI](https://github.com/fireflyframework/fireflyframework-dotnet/actions/runs/25544085183)

Next step

## Read the Orders service sample.

[Read the documentation](https://github.com/fireflyframework/fireflyframework-dotnet/blob/e3bcb1eb4a2a77551a8c16414e6a61f5a14b5a33/docs/README.md) [Open the sample](https://github.com/fireflyframework/fireflyframework-dotnet/tree/a41278325edd462a3fbcda096dd6cc44e48e908f/samples)
