Add .NET 10 support#2188
Conversation
Co-authored-by: jzabroski <[email protected]>
Co-authored-by: jzabroski <[email protected]>
Co-authored-by: jzabroski <[email protected]>
|
@copilot Update the azure pull requests pipeline yaml file to support .net 10 so that we can build this. |
Co-authored-by: jzabroski <[email protected]>
Updated both Azure pipeline files to support .NET 10:
Commit: bf0cb74 |
|
Do you think it would be a good idea to centralize all the supported framework TFMs in a single file ? |
There was a problem hiding this comment.
Can't it be simplified to this ?
<FluentMigratorTfm Condition="'$(MSBuildRuntimeType)' == 'Core'>$(TargetFramework)</FluentMigratorTfm>
<FluentMigratorTfm Condition="'$(MSBuildRuntimeType)' == 'Full'">net48</FluentMigratorTfm>
| <MigrationAssembly>$(MSBuildThisFileDirectory)..\FluentMigrator.Example.Migrations\bin\$(Configuration)\netstandard2.0\FluentMigrator.Example.Migrations.dll</MigrationAssembly> | ||
| </PropertyGroup> | ||
| </When> | ||
| <When Condition="'$(TargetFramework)' == 'net8.0' "> |
There was a problem hiding this comment.
Here too, I think a single Otherwise would be enough
|
any updates on this? looks like more of less done to me? |
|
do we have an ETA for this to be merged guys ? we love FM and use it heavily across number of projects, right now the FM CLI that we use to generate migration scripts is the only blocker for our .net 10 migration... |
|
Hello, Thanks in advance 🙏 |
|
Sorry for the delay - life got pretty busy. I will release it tonight. @PhenX some features you are working on will have to go in 8.1. |
|
@jzabroski oh, no security labels? |
|
I wanted to add it but I also acknowledge I have been tardy releasing .NET 10 support for no real good reason at all other than not clicking Generate Release Notes. |
Adds
net10.0to TargetFrameworks in projects that already target bothnet8.0andnet9.0.Changes
Added
net10.0to TargetFrameworks in 8 project files:FluentMigrator.DotNet.CliFluentMigrator.MSBuildFluentMigrator.Runner.SqlServerExample.MSBuild,Example.Migrations,Example.Migrator,Example.TypeMapperUpdated
Directory.Packages.propswith FluentMigratorTfm condition fornet10.0Made target framework conditions explicit in
FluentMigrator.Example.MSBuild.csprojChoose block (replaced Otherwise clause with explicitnet10.0condition)Updated Azure DevOps pipeline configurations to support .NET 10:
azure-pipelines-pullrequests.yml: Added .NET 10.x SDK installation with .NET 9.x and 8.x runtime supportazure-pipelines.yml: Updated to use .NET 10.x SDK (instead of 9.x) with .NET 9.x and 8.x runtime support for backward compatibilityAll changes follow existing patterns established for
net8.0andnet9.0.Original prompt
<issue_description></issue_description>
<agent_instructions>In places where the TargetFrameworks include net8.0 and net9.0, add net10.0.</agent_instructions>
Comments on the Issue (you are @copilot in this section)
@jzabroski Yes, it's coming. Just squaring away some issues with the release pipeline for GitHub Actions.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.