Completed
.NET Core 3.0 support (at least for geometric kernel)
Alberto Bencivenni
We don't want to be left behind and would like to move to Core 3.0 as soon as possible.
So we have a need to run Eyeshot geometry translations in a library compatible with Core 3.0. Core 3.0 has lost all compatibility with .NET framework. We have no pressing need to do our translations on anything else that Windows (i.e. Azure WebApp in our case). Of course, if you would do the right thing and separate the non UI/Windows parts to a generic geometry/translation lib running under Core 3.0 we and others could run that under Linux as well.
17
Comments
Thanks for your comment Matteo. Are you interested in the geometric kernel only or in User Interface too? If I well remember, you are using UI in your products.
Thanks for the quick feedback Alberto. You're right, we use UI as well.
All the discussion here is for the geometric kernel, for User Interface we have no plans yet.
I think porting everything to .NET Core should have higher priority since it's probably keeping a lot of people back from migrating from .NET Framework.
Eyeshot is one of the (if not the only) dependency that is preventing us from migrating and it's frustrating to know that it still won't happen for a while.
Like Matteo said, can you please provide us with some kind of timeline for this?
We will be soon able to provide a timeline for geometric kernel only.
Regarding UI, if you are targeting Windows only, would you accept to link Eyeshot .NET 4.7.2 DLLs to a .NET Core/Standard VStudio project?
Well linking a non standard dll (.net 1.0 to .net 4.8) within a .net standard (5.0, 6.0 so far) will only work if the non standard library does not use any api the standard has. Right now the UI make use of at least the bitmap class which was the first to error i got when i tried upgrading to .net 6.0. We have to wait for a UI upgrade before using the UI. Maybe it's a different story with WPF under .net 6.0 but in WinForms the code has been completely redone and is not at all compatible with the old non standard .net.
I suppose we could use .NET 4.8 for UI, then reference only .NET Standard 2.0 projects, but that would require a huge refactoring effort and we get a limited API, as well as still not being able to use the latest versions of certain libraries. For example EF Core targeted .NET Standard 2.0 up to version 3, but anything beyond that required .NET 5/6+, so we are stuck with EF Core 3 and cannot use its latest features until we upgrade.
It's not the end of the world for us of course, but would be nice not to be stuck with .NET Framework for many more years...
Could be a temporary solution, but if there's no commitment to port the whole component to the state-of-the-art stack I can't see our product to stay in a midway state for a prolonged time. Moreover, it has to be seen if this hybrid solution could run smoothly.
Hello,
is there any progress here. At least for the geometric kernel?
As far as i know there is a problem with the licensing.
When can we expect to get a version that can be used in a .Net 6 Project
Best Regards
We're glad to announce that we have a .NET6 Geometry library ready for the beta test 🎉
It's an early version, but every brave customer that wants to start testing it will be welcome! 🥳
If you want to join the beta tester program, please open a support ticket to receive more details.
Please sign in to leave a comment.