.Net Core 8

Rhino Developer
,
1

I may be jumping the gun here, but I noticed this:

image
image442×335 17 KB

…but I can’t find any mention anywhere of Rhino supporting plugins in .Net Core 8 yet. Apologies if I just missed it.

Are we moving to .Net Core 8 yet, or are there good reasons to stick with .Net Core 7 for a while longer yet. When can we stop supporting .Net Framework?

Arthur

1 Like
2

Rhino 8 supports .Net Core 7/.Net Framework 4.8.

We don’t change development frameworks midstream of a release.

Rhino 9 will use something newer.

— Dale

1 Like
3

I experimented with it in my own simple test project and net8 was fully usable。

4

Alright - so .Net Core 8 is offered, and it seems to work, but it’s not supported…

The Visual Studio alerts about the microsoft-unsupported .Net Core 7.0 are concerning, but I guess it is what it is.

5

Why?

— Dale

6

Hi Dale,

Maybe it’s that you know more about this than I do, but here is the alert that Visual Studio has been throwing me:

“The target framework ‘net7.0’ is out of support and will not receive security updates in the future. Please refer to .NET and .NET Core official support policy for more information about the support policy.”

Maybe I don’t know what a security update for the framework entails. Why should or shouldn’t I be concerned, for myself or my users?

Arthur

7

Hi Arthur,
We don’t want to introduce potential new issues by switching the runtime in a stable version of Rhino. It is possible to have Rhino run with .NET 8, but we don’t make that the default configuration.

8

Hi Steve,

It’s obvious enough why you would stick with an older runtime, and I’m not advocating that you change your approach here. I was a little hopeful that the addition of v8 in the setdotnetruntime command might mean we could compile our tools for .Net 8, and use a supported runtime.

Absent that, the question has become, should I be concerned about using an unsupported dotnet core 7 runtime, and why or why not?

Arthur

1 Like