Release a new version

[jcs090218]

I think there are multiple bug fix. Maybe is good to tag a new release? 😕

[Isitar]

push

[var1ap-WA]

[fossbrandon]

Is there an update on when we might get a new release? The projects I'm using this with require features that are not released yet so I have to bring the project into my own project and reference it that way.

[IgorMilavec]

@drieseng could you publish a preview NuGet package? This way users will be able to access the latest features and bug fixes from the development branch and we would gain feedback if the code is stable enough.

[drieseng]

@IgorMilavec I'll try to find time in the next days. Releasing a new version is a pain (until we remove support for legacy target frameworks).

[IgorMilavec]

I know, that's why I'm trying to push towards vNext so we can release the final legacy version and then remove legacy frameworks. :)

[chrcar01]

Any chance of getting a new release of what's currently in the develop branch?

[Shadow-of-N7]

[WojciechNagorski]

@Shadow-of-N7 @var1ap-WA @chrcar01 https://twitter.com/WojtekNagorski/status/1711675545061110039

[Rob-Hague]

Completed by #1201

[mhm-iteris]

Is it just possible to make another repo with .NET core 6 and push out a nuget package? Isolating .NET and .NET framework from one another is probably best.

[Rob-Hague]

Is it just possible to make another repo with .NET core 6 and push out a nuget package? Isolating .NET and .NET framework from one another is probably best.

In what way? I see no reason to do that.

[mhm-iteris]

Is it just possible to make another repo with .NET core 6 and push out a nuget package? Isolating .NET and .NET framework from one another is probably best.

In what way? I see no reason to do that.

Ah... Let me explain a little more clearly. .NET Framework and .NET core are vastly different frameworks with different lifecycle support policies by Microsoft. Microsoft is phasing out support for .NET framework, but will continue to support 4.7.2- 4.8.1 under their OS support policies. They have agreed to stop developing features for .NET framework. Details in below links:

https://learn.microsoft.com/en-us/lifecycle/products/microsoft-net-framework
https://learn.microsoft.com/en-us/lifecycle/faq/dotnet-framework

From a high level perspective the team would have to support 2 different versions of this package anyway. Where .NET Core will be more frequently updated. My suggestion would be to have 2 separate repos, one for .NET Core (updated frequently) and .NET framework (updated only for security issues). Splitting the codebase will result in less work to develop .NET core codebase as Nuget packages, less work to regression test, and faster deployments for .NET core (majority of users will switch over to).

[Rob-Hague]

Thanks. I understand the difference between Framework and Core, but 99% of the code base for this project is shared between the targets, so in reality it would be twice as much work to maintain two repos. It is very common (and well supported) for a library project to target both.

Long term, I expect the project to simply drop Framework and Standard targets. But there is plenty of modernizing and bug-fixing to be done with the current targets before that point.

[WojciechNagorski]

I agree with @Rob-Hague.