Workflow.csproj

<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <RootNamespace>Workflow</RootNamespace>
    <AssemblyName>Workflow</AssemblyName>
    <IsPackable>false</IsPackable>

    <!--
      NativeAOT is deliberately NOT enabled here, and the reason is the sample's whole
      point rather than an omission. This flow declares `Durable`, a durable flow is
      refused without a journal, and the only journal FlowX ships is PostgreSQL — so this
      project references Npgsql, which the ecommerce sample does not. Turning PublishAot on
      would make constraint C2's smoke test depend on a driver this repository does not
      own. `samples/ecommerce` stays the AOT arm, with nothing behind it; this one is the
      arm with a database behind it. The README says which sample proves which property.
    -->
    <InvariantGlobalization>true</InvariantGlobalization>
  </PropertyGroup>

  <ItemGroup>
    <!--
      The in-memory adapters are internal: they are infrastructure, not part of the
      sample's story. The test project sees them rather than the sample widening its
      surface to be testable — the same bargain samples/ecommerce strikes.
    -->
    <InternalsVisibleTo Include="Workflow.Tests" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="../../src/FlowX.Abstractions/FlowX.Abstractions.csproj" />
    <ProjectReference Include="../../src/FlowX.Core/FlowX.Core.csproj" />
    <ProjectReference Include="../../src/FlowX.Runtime/FlowX.Runtime.csproj" />
    <ProjectReference Include="../../src/FlowX.Hosting/FlowX.Hosting.csproj" />
    <ProjectReference Include="../../plugins/FlowX.Http/FlowX.Http.csproj" />

    <!--
      The journal. `samples/ecommerce` needs no store because it is Ephemeral; this one
      cannot start without one, which is the price of the profile it declares and the
      reason the two samples are different applications rather than one.
    -->
    <ProjectReference Include="../../plugins/FlowX.Postgres/FlowX.Postgres.csproj" />

    <!--
      The compiler as an ANALYZER, not a library — so the generator runs inside this
      project's build against this project's source, exactly as it would for a consumer.
      This sample is the only place in the repository where it is handed a flow that
      forks, loops, branches, switches and composes a child all at once.
    -->
    <ProjectReference Include="../../src/FlowX.Compiler/FlowX.Compiler.csproj"
                      OutputItemType="Analyzer"
                      ReferenceOutputAssembly="false"
                      Condition="'$(FlowXGeneratorDisabled)' != 'true'" />
  </ItemGroup>

</Project>