Moving to .NET5 and .NET6

[amerkoleci]

Hi guys,
.NET 6 is arround the corner and I plan to move from .NET Standard 2.0 to .NET5 e .NET6, to take advantage of new language features and improvements (MemoryMarshal, Span) etc.

If you find any trouble feel free to suggest.

@SuRGeoNix, @h1cks, @andrew-boyarshin

[SuRGeoNix]

I think by removing .NET standard 2.0 support will brake the compatibility with .NET Framework. Correct if I'm wrong here!

Related source

[h1cks]

I'm supportive of the move to .NET 6.0 once its mainstream and part of the releases for win 10/11.

I shot myself in the foot when I moved to .NET 5.0 before it became a full release on win 10 (rather than a download from MS). The interaction with triggering the .NET 5.0 download broke because MS moved it's on download page.

I'm building in .NET 5.0 at the moment, but still using Sharpdx (until I get the FMV working). I agree with @SuRGeoNix though, my tools are written WPF .NET framework, which might pose an issue for me if .NET Framework breaks (when I migrate my tools to Vortice).

Edit: Windows Forms also supports .NET Core 3.1 and .NET 5.0 which is my real concern so there maybe no issue for me here.

[amerkoleci]

WPF and Windows Forms can already be used with .NET5-windows and .NET6-windows, so thats no more an issue.
I think in meanwhile I can move to .NET 5 and wait for .NET 6 once release ofc.

[h1cks]

I have been running my tools with .NET 5.0, I'm not completely familiar with the underlying .NET Standard 2.0 compatibility issues of retiring. From what I understand, .NET Standard 2.0 seems to be caught in the middle of .NET Core/.NET. Is this assumption correct?

[amerkoleci]

I have been running my tools with .NET 5.0, I'm not completely familiar with the underlying .NET Standard 2.0 compatibility issues of retiring. From what I understand, .NET Standard 2.0 seems to be caught in the middle of .NET Core/.NET. Is this assumption correct?

Yes, but I don't plan to support for so long legacy .NET framework, .NET5 is out

[h1cks]

I see no issues with the migration at the end of the day. The library is relatively new, and will garner more support as compatibility in Sharpdx falls off and associated projects need the new and more modern frameworks. Your project is very important in terms of the current landscape of DX/C#

[andrew-boyarshin]

I'm against this move. .NET Standard (+ .NET Framework) is still too popular to be dismissed. SharpGen even supports 1.1+ (will become 1.3+ soon, though). I understand that you don't want to add too many TFMs (like SharpGen.Runtime does, to support the widest range of implementations possible, but use the most performant implementation on each one). There is only one difference between the code generated by SharpGen for .NET versions: .NET 5+ function pointers. I propose adding net5.0 TFM to all projects, but keeping netstandard2.0, thanks to System.Memory NuGet package. Do you really need to require .NET Core? Popular and important projects like Avalonia still support .NET Standard 2.0, and, from what I gather, there are no immediate plans for that to change.

[andrew-boyarshin]

@amerkoleci SharpGen bug in Sdk.targets. Proposed workaround: do not depend on multi-TFM projects (like DXGI) until the fix is made. Or switch to PackageReference, but that's harder.

[amerkoleci]

Do you plan to fix this bug? Otherwise can you send me workaround pr please?

[andrew-boyarshin]

I think I can make a hotfix, yeah. ETA: 24 hours.

[amerkoleci]

Don't worry, no rush! Thank you

[amerkoleci]

I think I can make a hotfix, yeah. ETA: 24 hours.

Any news here dude?