Skip to content

fix: pin .NET Framework reference assemblies for consistent lock file #185

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
esskar merged 1 commit into from
Jun 16, 2026
Merged

fix: pin .NET Framework reference assemblies for consistent lock file #185

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions src/Serialize.Linq/Serialize.Linq.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,19 @@
<WarningLevel>7</WarningLevel>
</PropertyGroup>

<!--
Reference the .NET Framework reference assemblies explicitly for the
net48/net481 targets. On non-Windows build hosts the SDK pulls this package
in implicitly (the reference assemblies aren't installed), but on Windows
they come from the OS and no package is added. Declaring it explicitly keeps
packages.lock.json identical across build operating systems so locked-mode
restores don't fail in CI. PrivateAssets="all" keeps it build-only and out
of the published package's dependencies.
-->
<ItemGroup Condition=" '$(TargetFramework)' == 'net48' or '$(TargetFramework)' == 'net481' ">
<PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3" PrivateAssets="all" />
</ItemGroup>

<ItemGroup Condition=" '$(TargetFramework)' == 'net6.0' ">
</ItemGroup>

Expand Down
Loading