Skip to content

Fix screenplay generate in published builds #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
woksin merged 2 commits into from
Jul 30, 2026
Merged

Fix screenplay generate in published builds #58

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6caaaaa
Ship Microsoft.CodeAnalysis.Workspaces with published builds
woksin Jul 30, 2026
1b45054
Keep the Roslyn build host on disk in single-file publishes
woksin Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions Source/Cli/Cli.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,16 @@
<DefineConstants>$(DefineConstants);CRATIS_NATIVE</DefineConstants>
</PropertyGroup>

<!--
Roslyn evaluates MSBuild in a separate BuildHost process, which it starts from real files in a
BuildHost-netcore folder next to the executable. Bundling those into the single file leaves that folder
holding nothing runnable, so 'cratis screenplay generate' fails with the build host missing. Self-extraction
puts them back on disk at startup and keeps the single file the native downloads ship.
-->
<PropertyGroup Condition="'$(PublishSingleFile)' == 'true'">
<IncludeAllContentForSelfExtract>true</IncludeAllContentForSelfExtract>
</PropertyGroup>

<ItemGroup>
<PackageReference Include="Cratis.Arc.Screenplay" />
<PackageReference Include="Cratis.Chronicle.Connections" />
Expand All @@ -43,6 +53,13 @@
<PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" />
<!-- MSBuild itself must come from the installed SDK that MSBuildLocator registers, never from the output folder. -->
<PackageReference Include="Microsoft.Build.Framework" ExcludeAssets="runtime" PrivateAssets="all" />
<!--
The repository default treats Workspaces.Common as an analyzer-only dependency, and PrivateAssets="all"
keeps Microsoft.CodeAnalysis.Workspaces.dll out of publish output while still copying it on build - so a
developer machine works and every shipped build fails. The Screenplay commands load that assembly at
runtime, so here it has to be a real dependency.
-->
<PackageReference Update="Microsoft.CodeAnalysis.Workspaces.Common" PrivateAssets="none" />
</ItemGroup>

<ItemGroup>
Expand Down
Loading