SabreTools/SabreTools.Serialization
1
0
Fork 0
mirror of https://github.com/SabreTools/SabreTools.Serialization.git synced 2026-04-12 01:03:10 +00:00
Code Issues 56 Packages Projects Releases 20 Wiki Activity
Files
main
SabreTools.Serialization/SabreTools.Serialization.CrossModel.Test/SabreTools.Serialization.CrossModel.Test.csproj

22 lines
834 B
XML
Raw Permalink Normal View History

Libraries This change looks dramatic, but it's just separating out the already-split namespaces into separate top-level folders. In theory, every single one could be built into their own Nuget package. `SabreTools.Serialization` still builds the normal Nuget package that is used by all other projects and includes all namespaces.
2026-03-21 16:26:56 -04:00
<Project Sdk="Microsoft.NET.Sdk">
Copy serialization tests from SabreTools.Test, fix issues
2024-04-24 13:23:51 -04:00
Add .NET 9 to target frameworks
2024-11-13 02:42:14 -05:00
<PropertyGroup>
Add support for .NET 10
2025-11-14 09:06:59 -05:00
<TargetFrameworks>net8.0;net9.0;net10.0</TargetFrameworks>
Add .NET 9 to target frameworks
2024-11-13 02:42:14 -05:00
<IsPackable>false</IsPackable>
<LangVersion>latest</LangVersion>
<Nullable>enable</Nullable>
</PropertyGroup>
Copy serialization tests from SabreTools.Test, fix issues
2024-04-24 13:23:51 -04:00
Add .NET 9 to target frameworks
2024-11-13 02:42:14 -05:00
<ItemGroup>
Libraries This change looks dramatic, but it's just separating out the already-split namespaces into separate top-level folders. In theory, every single one could be built into their own Nuget package. `SabreTools.Serialization` still builds the normal Nuget package that is used by all other projects and includes all namespaces.
2026-03-21 16:26:56 -04:00
<PackageReference Include="coverlet.collector" Version="8.0.1" />
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.3.0" />
Update to IO 2.0.0
2026-03-24 18:02:49 -04:00
<PackageReference Include="SabreTools.Hashing" Version="[2.0.0]" />
Libraries This change looks dramatic, but it's just separating out the already-split namespaces into separate top-level folders. In theory, every single one could be built into their own Nuget package. `SabreTools.Serialization` still builds the normal Nuget package that is used by all other projects and includes all namespaces.
2026-03-21 16:26:56 -04:00
<PackageReference Include="xunit" Version="2.9.3" />
<PackageReference Include="xunit.runner.visualstudio" Version="3.1.5" />
Add .NET 9 to target frameworks
2024-11-13 02:42:14 -05:00
</ItemGroup>
Copy serialization tests from SabreTools.Test, fix issues
2024-04-24 13:23:51 -04:00
Add .NET 9 to target frameworks
2024-11-13 02:42:14 -05:00
<ItemGroup>
Libraries This change looks dramatic, but it's just separating out the already-split namespaces into separate top-level folders. In theory, every single one could be built into their own Nuget package. `SabreTools.Serialization` still builds the normal Nuget package that is used by all other projects and includes all namespaces.
2026-03-21 16:26:56 -04:00
<ProjectReference Include="..\SabreTools.Serialization.CrossModel\SabreTools.Serialization.CrossModel.csproj" />
Add .NET 9 to target frameworks
2024-11-13 02:42:14 -05:00
</ItemGroup>
Copy serialization tests from SabreTools.Test, fix issues
2024-04-24 13:23:51 -04:00
Add .NET 9 to target frameworks
2024-11-13 02:42:14 -05:00
</Project>
Reference in New Issue Copy Permalink