Port to .NET Core

[takeoshigeru]

Hello,

I wanted to target a .NET Standard 2.1 (.NET Core >= 3) library from a Bannerlord SubModule but current TaleWorlds assemblies target .NET Framework 4.7.2. Is it a limitation of the engine? Would you know the reason why it doesn't target the last .NET Framework version (4.? Is there some plan to port Bannerlord to .NET Core?

In November 2020, Microsoft will introduce .NET 5. Could it be an opportunity to migrate Bannerlord and benefit from the huge performance improvements and awesome features like the Pinned Object Heap?

 

[ptp]

I was wondering the same thing. Is there a specific compatibility reason for using .NET Framework? What technology or platform does the engine use that is not supported in .NET Core or .NET 5?

@Mustafa Korkmaz

 

[Mustafa Korkmaz]

We're using VS2017, which doesn't have .NET Standard 2.1 as far as I know. We may migrate to VS2019 in the future though.

 

[Kiyakkoray]

Actually most of our DLL files are targeting .NET Standard 2.0. In fact, we are using .NET Core on our server systems(which shares lots of dll files with client itself). So there is nothing stops us from using .NET Core on clients as well. We'll discuss it internally.

Thank you...

 

[takeoshigeru]

Glad to hear that Please share your decision with us in the future

 

[ptp]

Great!
Have you tested running the client using .NET core or .NET 5.0 RC? It will be interesting to find out if and how much if any performance boost it gives.

@Kiyakkoray @Mustafa Korkmaz

 

[takeoshigeru]

We'll discuss it internally.

@Kiyakkoray Any news? Note that the migration would be a breaking change for modders but it's for the greater good