Steema Central

Hello,

bairog wrote: ↑

Wed Oct 13, 2021 7:56 am

Are there any news about it?
Does TeeChart.NET is now .NET 5 ready annoncement at you forum means that this is finally fixed?
Or maybe on latest .NET 6.0 RC2 or with latest Visual Studio 2022 RC/Preview 5?

Using the code on the issue itself, I've just run it using .NET 6 SDK version 6.0.100-rc.2.21505.57 in Microsoft Visual Studio Enterprise 2022 Preview (64-bit) Version 17.0.0 Preview 5.0, using .NET 6 as the target Framework in the Core4451 project. Unfortunately the issue can still be reproduced - it works in .NET Framework 4.8, but doesn't work in .NET 6.

On the issue itself I see they've changed the milestone from .NET 6 to .NET 7:
I'm therefore not sure what more we can do at this stage to resolve this issue.

Christopher wrote: ↑

Thu Oct 14, 2021 8:30 am

Using the code on the issue itself, I've just run it using .NET 6 SDK version 6.0.100-rc.2.21505.57 in Microsoft Visual Studio Enterprise 2022 Preview (64-bit) Version 17.0.0 Preview 5.0, using .NET 6 as the target Framework in the Core4451 project. Unfortunately the issue can still be reproduced - it works in .NET Framework 4.8, but doesn't work in .NET 6.

I've duplicated the description of you experience on the issue topic.

Christopher wrote: ↑

Thu Oct 14, 2021 8:30 am

On the issue itself I see they've changed the milestone from .NET 6 to .NET 7:

As RussKie said The designer is separate from the .NET version, it is part of Visual Studio and updates with each new VS preview.
So looking foward for finally fixing that in one of the upcoming Visual Studio 2022 previews..

Christopher wrote: ↑

Mon Jan 11, 2021 10:50 am

Let's see if we get a response to this:
https://github.com/dotnet/winforms/issues/4451

Hello again.
I've recently created another issue on github regarding docs for WinForms Designer SDK (that are vital for finally implementing chart editor box on .NET 5). Some days ago I've tagged your github account, but if you missed that - yesterday they posted a repo with sample code and starting points to investigate.
Good luck.

Hello,

yes, thank you, I saw that—in fact over two weeks previous to tagging me into that conversation of yours I'd added id=2516 to our issue tracker.

I very much agree with @kirsan31's comment on that thread—it seems to me ridiculous that we should have to pack a NuGet into our Charting control to enable the Visual Studio designer to work as expected. I also agree that Microsoft has recently made the most disagreeable U-turns on its plans (.NET Standard 2.0 support for UWP comes to mind), so with @kirsan31 I also hope this is the worst thing that's going to happen to WinForms in .NET Core.

Christopher wrote: ↑

Thu Apr 14, 2022 7:48 am

it seems to me ridiculous that we should have to pack a NuGet into our Charting control to enable the Visual Studio designer to work as expected

Yes this looks strange.

Christopher wrote: ↑

Thu Apr 14, 2022 7:48 am

I also agree that Microsoft has recently made the most disagreeable U-turns on its plans

I'm afraid I don't quite understand what you're talking about. Can you provide some details.

bairog wrote: ↑

Thu Apr 14, 2022 8:05 am

Christopher wrote: ↑

Thu Apr 14, 2022 7:48 am

I also agree that Microsoft has recently made the most disagreeable U-turns on its plans

I'm afraid I don't quite understand what you're talking about. Can you provide some details.

A good place to start to understand the UWP issue is here.

Hello,

the latest version of TeeChart v4.2022.4.26 has a reference to the beta-version of Microsoft's SDK and seems to work well, at least following the tests we've done here.

We'd like to encourage you download and test this version of TeeChart, and to please let us know any problems you have with it.

Christopher wrote: ↑

Wed Apr 27, 2022 2:05 pm

We'd like to encourage you download and test this version of TeeChart, and to please let us know any problems you have with it.

I've peformed a simple test - TeeChart v4.2022.4.26 works fine. Finally you've made it (just 2 weeks before .NET 5 EOL ), many thanks.
Latest TeeChart v4.2022.5.16 crashes when trying to add a new chart - but looks like you already know about some problems in this version of package as you've already deleted this version from nuget

bairog wrote: ↑

Wed May 18, 2022 10:57 am

I've peformed a simple test - TeeChart v4.2022.4.26 works fine. Finally you've made it (just 2 weeks before .NET 5 EOL ), many thanks.
Latest TeeChart v4.2022.5.16 crashes when trying to add a new chart - but looks like you already know about some problems in this version of package as you've already deleted this version from nuget

Glad to hear it works for you! And you're right, Microsoft certainly did drag their heels on this one as you've been able to see for yourself on GitHub. The latest public version is now v.4.2022.5.18 and will include the .NET 5.0 build until it reaches end of life. I see .NET 7.0 is now in preview 4, although I'm not sure we're going to make a build for it given that our .NET 6.0 build is LTS.

Christopher wrote: ↑

Wed May 18, 2022 11:46 am

The latest public version is now v.4.2022.5.18 and will include the .NET 5.0 build until it reaches end of life.

.NET 5.0 already reached EOL 8 days ago (10 May 2022) Decpite of that I hope you will not drop .NET 5.0 support in following builds - like many other developers I'm stuck on Visual Studio 2019 and maximum .NET 5.0 for an indefinite time.

bairog wrote: ↑

Wed May 18, 2022 11:57 am

.NET 5.0 already reached EOL 8 days ago (10 May 2022)

Ah yes, I see that they released a new build of .NET 5.0 on the same day they ended its life. I had hoped Microsoft would support this last version of theirs for a few months before ending its life but no, you're right, it seems they prefer to release new binaries with no support at all.

bairog wrote: ↑

Wed May 18, 2022 11:57 am

Decpite of that I hope you will not drop .NET 5.0 support in following builds..

I'm not sure if you're being serious here or not—is it true that your preference is to keep using the .NET 5.0 version of TeeChart rather than moving to the already-available .NET 6.0 version? And if so, could I please ask you what your motivations are for doing so?

Christopher wrote: ↑

Wed May 18, 2022 12:09 pm

I had hoped Microsoft would support this last version of theirs for a few months before ending its life but no, you're right, it seems they prefer to release new binaries with no support at all.

Yes that looks really strange..

Christopher wrote: ↑

Wed May 18, 2022 12:09 pm

I'm not sure if you're being serious here or not—is it true that your preference is to keep using the .NET 5.0 version of TeeChart rather than moving to the already-available .NET 6.0 version? And if so, could I please ask you what your motivations are for doing so?

Unfortunatelly I'm serious. My motivation is pretty simple (and lots of developers unfortunatelly have the same) - Visual Studio 2019 doesn't officially support .NET 6 development. But purchasing a bunch of Visual Studio 2022 licenses in not so easy (and quick) task in large enterprise organisations (the one I'm working in). So I'm stuck on .NET 5.0 for an indefinite time.

bairog wrote: ↑

Wed May 18, 2022 12:21 pm

Unfortunatelly I'm serious. My motivation is pretty simple (and lost of developers unfortunatelly have the same) - Visual Studio 2019 doesn't officially support .NET 6 development. But purchasing a bunch of Visual Studio 2022 licenses in not so easy (and quick) task in large enterprise organisations (the one I'm working in). So I'm stuck on .NET 5.0 for an indefinite time.

Thank you for your explanation, it is really useful to us. I now have a very clear idea of your situation, and will recommend to my colleagues that we do not pull the .NET 5.0 version out of our NuGet packages for the time being.

Christopher wrote: ↑

Wed May 18, 2022 12:36 pm

Thank you for your explanation, it is really useful to us. I now have a very clear idea of your situation, and will recommend to my colleagues that we do not pull the .NET 5.0 version out of our NuGet packages for the time being.

Thank you, really hope they will hear you. BTW the same situation will appear again in December - some developers (that are stuck on Visual Studio 2019 like me) really suppose downgrade to .NET Core 3.1 (older, but still supported for some time) a better alternative than staying on unsupported .NET 5.0. Hope your colleagues will also don't drop .NET Core 3.1 support as soon it reaches EOL.
Many thanks.