Bring back .net5.0?

[starteleport]

Hi! Thanks for the great tool.

As I see, you've dropped support for .net 5.0 in #44. Any chance dotnet-repl could run both on 5.0 and 6.0?

[jonsequitur]

Thanks for the kind words.

When .NET Interactive supports different TFMs or SDKs, then dotnet repl will be able to do so as well, but it's not a problem we're working on right yet. We updated to .NET 6 because it's the latest version and .NET 5 goes out of support in May.

Is there something specific you want to do that you need .NET 5 for? Understanding your scenario might help us think about how to prioritize a multiple-TFM feature in .NET Interactive.

[starteleport]

Well, not that specific in fact.

We just have not started migration to .NET 6 yet. But I am sure there are lots of projects that are not even .NET 5. Thus REPL that targets some earlier frameworks may be of interest. As I see, Microsoft.DotNet.Interactive is netstandard2.1 and Spectre.Console is netstandard2.0 so it seems attainable at a first glance.

[sergiofagostinho]

Just to add to what @starteleport said, many teams/companies (such as the one I work on ;)) tend only use LTS versions of .NET. As such, pinning each repl release to the latest .NET version at the moment is a bit inconvenient. As an example, I've started using the tool recently and I use .NET 6 on my machine, so the latest version repl version didn't work (as it's pinned to .NET 7). It wasn't a deal breaker as I was sufficiently motivated to find a version that was built for .NET 6, but some users might have just given up on the tool on the spot.