Posted 6 months ago by Miguel A.
Version: 18.1.0673
Avatar

Hi,

with .NET core 3.0 Microsoft allows WPF applications to target .NET core. Because of the performance improvements and the fact that Microsoft decided to not support the framework with new features anymore, I'm probably switch as soon as possible. I'm curios if you have taken a look at it already or if you plan any support for .NET core including eventually beta releases? I think final release of .NET core 3.0 is around late 2019, first beta end of this year.

Comments (6)

Posted 6 months ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Miguel,

At the moment, most of our development resources are working on completing the massive SyntaxEditor vNext project, which will unify the WPF, UWP, and WinForms SyntaxEditors under the same API.  Once that is finished and stabilized, we will be looking at other areas.  I've bumped up priority on looking at moving to .NET 3.0 to see what's involved.  That is something we will want to get into sometime in the coming months.


Actipro Software Support

Posted 2 months ago by Dirk Zellerfeld
Avatar

Hi,

we're interested too in this question. Are there any news? Your competitors mostly all have .NET Core supported.

Posted 2 months ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Dirk,

When running the Microsoft Portability Analyzer on the recent WPF control DLLs of ours, they are pretty much 100% compatible other than one call in SyntaxEditor and three calls in the Text.Addons.DotNet assembly.  That being said, running a stub .NET Core 3 app in VS 2019 with all of those products in use seems to be working fine.

Now that VS 2019 is near final release, we will be looking into all this more soon.  From your perspective and anyone reading this, what can we do to make sure that everything is configured optimally for your needs?

I assume you'd like to see pre-compiled .NET Core 3 assemblies distributed side-by-side with the normal .NET Framework versions via our controls installer?  Or is using the existing .NET Framework assemblies fine?  What else would you like?  Please be as detailed as possible.  Thanks!

[Modified 2 months ago]


Actipro Software Support

Posted 2 months ago by Dirk Zellerfeld
Avatar

Hi,

we like to drop .NET Framework dependency completely and make our app self-contained running everywhere on all computers. We already did that with another application and it was a huge success. At the moment lots of support inquiries we receive are all .NET Framework dependency related, this costs us a lot of time and money.  This is why we would like to not going the way of .NET Framework / .NET Core mix-up, although you are right this is currently possible. So you are right that pre-compiled .NET Core 3 assemblies are mandatory and should be distributed either side-by-side or by separate installer.

I see a lot .NET developers porting their software to .NET Core and I agree with Miguel the rapid development, massive improvements and the fact that its open source are the main reasons but also that, although Microsoft said they will continue to support .NET Framework, all new features will be mainly .NET Core exclusively.

Maybe in the long run you could take a look and see if WPF Studio can benefit performance whise from all the new features in .NET Core like Span<T> or hardware infragistics but at first and especially as long as .NET Core is not a final product pre-compiled binaries without any changes should be enough.

Thanks for taking a look at it, we are really looking forward to it.

Posted 1 month ago by Dirk Zellerfeld
Avatar

Hi,

is there any news on this? Do you plan to release .NET Core binaries on vNext release?

Posted 22 days ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Dirk,

We had e-mailed you over a week ago to try and get some private feedback but never got a reply.  I wanted to check in and see if your received the e-mail from our support address?  Perhaps check your spam folder if you didn't.


Actipro Software Support

The latest build of this product (v2018.1 build 0676) was released 0 days ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.