-
Dear Community Members, From my understanding, the latest stable Orchard Core version, 2.1.7, offers compatibility with .NET 8. However, I also gather that it may not yet be fully compatible with .NET 9. To help in planning our curriculum and development environment, could someone perhaps point me towards the latest roadmap for Orchard Core, particularly concerning its support for newer .NET versions? This would be invaluable in making informed decisions about the most suitable platform for my training initiatives moving forward. Kind Regards, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
The latest release supports both .NET 8 and 9. Could you please elaborate on the issues you are facing with .NET 9? |
Beta Was this translation helpful? Give feedback.
-
2.1.7 targets .NET 8 only (the latest |
Beta Was this translation helpful? Give feedback.
-
Dear Zoltán,
Thank you for your clarification in the thread. I wanted to follow up on
your point regarding the .NET versions. Specifically, I didn't fully grasp
the meaning of your statement that "the latest \`main\` dual-targets 8 and
9".
As someone who is relatively new to the Orchard Core project, I would be
very grateful if you could elaborate a little on what it means for the
\`main\` branch to "dual-target" .NET 8 and .NET 9. Could you perhaps
explain the implications of this for developers, and how it relates to the
current stable release, version 2.1.7, which I understand targets only .NET
8? Any additional details you could provide on this topic would be very
helpful for my understanding.
To further clarify my point: can I please ask you to have a look at my
GitHub repo for the OC project at :
https://github.com/krchome/OC-CustomContentPartDemo (Built in OC 1.8.2 but
since then I have tested it working fine for 2.1.7 but with .NET 8.0 ) Now
will it work if I upgrade it to .NET 9.0. My query is what package
references shall I put for ex in the modules project file below :
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<Nullable>enable</Nullable>
<ImplicitUsings>enable</ImplicitUsings>
</PropertyGroup>
<ItemGroup>
<FrameworkReference Include="Microsoft.AspNetCore.App" />
<PackageReference Include="OrchardCore.Module.Targets" Version="1.8.2" />
<PackageReference Include="OrchardCore.ContentManagement" Version="1.8.2" />
<PackageReference Include="OrchardCore.ContentManagement.Abstractions"
Version="1.8.2" />
<PackageReference Include="OrchardCore.ContentTypes.Abstractions"
Version="1.8.2" />
<PackageReference Include="OrchardCore.Data.Abstractions" Version="1.8.2" />
<PackageReference Include="OrchardCore.Autoroute" Version="1.8.2" />
</ItemGroup>
</Project>
Forgive me if I have asked anything silly!
Thank you in advance for your time and assistance.
Best regards,
Kaushik
…On Mon, May 26, 2025 at 10:45 AM Zoltán Lehóczky ***@***.***> wrote:
2.1.7 targets .NET 8 only (the latest main dual-targets 8 and 9). That
doesn't prevent you from using the OC packages from a .NET 9 project.
—
Reply to this email directly, view it on GitHub
<#17959 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACAVBZ4NPWBWF5AKARKTLQ33AJBXHAVCNFSM6AAAAAB54HAMRKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRWGYZDONY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
2.1.7 targets .NET 8 only (the latest
main
dual-targets 8 and 9). That doesn't prevent you from using the OC packages from a .NET 9 project.