search

MarimerLLC / cslaforum

Discussion forum for CSLA .NET
https://cslanet.com
Other
31 stars 6 forks source link

WinForms/Asp.Net - Moving to .Net core #742

Open ajj7060 opened 5 years ago

ajj7060 commented 5 years ago

Question WinForms has a future, in .Net Core 3 it would seem. Which is great, because our main applications are still heavily winforms.

So its clear to us that we should start planning how to move our ducks to the .Net Core world, which would be really great for us as we can include .net without requiring our customers to install new versions of the .net framework.

This will take a lot of time though and we have yet to start planning anything even, but one thing that has me kinda worried. If we move our application server, currently hosted under IIS (and likley to remain so), it sounds like WCF doesn't make the cut over to Net Core. Which sounds like we'd want to use HttpPortal instead, which is fine, but the HttpPortalClient requires async only calls.

The problem is that our winforms code is pretty much all sync; worse, its sync on the UI thread, very little code makes use of doing expensive calls on non-UI threads. So with my understanding of things now, it seems like we're going to have to redo the forms code to take async background work into account. Which is doable, but will take a huge amount of time. Is that about the size of things, or is there something I'm missing that would let us tackle the non-async stuff after we get things to .Net core?

Version and Platform CSLA version: 4.10 OS: Windows Platform: WinForms, ASP.NET, WCF.

rockfordlhotka commented 5 years ago

I've already implemented synchronous support in HttpProxy in CSLA version 5.

ajj7060 commented 5 years ago

Awesome! That will be a huge help as we move to net standard/core.