.NET Core 3.0 support (at least for geometry kernel)

We don't want to be left behind and would like to move to Core 3.0 as soon as possible. We are on Core 2.2 at the moment (together with the compatible .NET framewotrk 4.72).

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.

4

Comments

7 comments
  • My thoughts on this topic:

    • separation of UI and generic geometry/translation is a good idea anyway. I interpret this as a strict separation between the UI control (currently named Model or Environment and currently in two types => WPF and WinForms) and the generic logic.
    • The generic part should be just a binary (or multiple) that is used when using the WPF controls or the WinForms control.
    • The generic part should be usable stand-alone => without any WPF nor WinForms dependencies
    • The licensing/unlock mechanism should work without the need to instantiate a WPF or WinForms control first and call Unlock() (which currently is the case)
    • The readers and writers should work with the generic part => no need for the UI control EVEN when generating a bitmap.
    • One additional UI control: Blazor => rendering to WebGL to use the Eyeshot control within the Browser including mouse interaction => this for Blazor type of scenarios.
    • All async commands being in line with the TPL syntax => names ending with Async and awaitable => e.g. await x.DoWorkAsync()

    Great product you have!

    Have a great weekend,

    Willem Dijkgraaf

     

    2
    Comment actions Permalink
  • What is the status of support for .NET Core 3.1?

    0
    Comment actions Permalink
  • Hi Magnus,

    We will start this project soon.

    1
    Comment actions Permalink
  • I agree with Willem 100%. In every point he makes.

    1
    Comment actions Permalink
  • Any news regarding this (the issue was originally reported by me)?

    0
    Comment actions Permalink
  • It's in Eyeshot 2021 Roadmap. Actually, we are preparing the DEV code line to allow these siamese twins (UI and geometric kernel) separation. Will we succeed? More news later this year.

    0
    Comment actions Permalink
  • Thanks for the update. Hopefully the twins will be separated this year. And I assume that you will also jump on the opportunity to package the geometric stuff into a potential new product (conversion for example). It's worth it.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post