Last post Apr 24, 2017 09:42 AM by Zhi Lv - MSFT
Apr 21, 2017 08:24 PM|Marty V|LINK
Long story short, I inherited a multilayered application that was developed back in the 80's, ported an untold number of times through the VB/.Net revolution (and evolution), landed partially on .Net 1/2, and was finally left on the chopping block for a
decade with all developers now long gone.
I've done a pretty good job at resurrecting the project, but am now faced with redoing the web services.
The project uses a WinForms client, ASP (1.x?)/ADO (SOAP) Web Service, and has a SQL back end.
Assuming nothing from the current Web Service is available to reuse, what technology from the .Net family would be advised to replace it, from the ground up, that can still interface well with SQL and WinForms? I'm looking for a current / not-going-to-die-anytime-soon
solution; I don't want to invest the time necessary for this rework on a framework that's going to be obsolete 'tomorrow'.
I had almost settled on .Net Core. However, from what I'm reading (could be misinformation, or misunderstood information), the version of CLR it uses isn't compatible with WinForms.
My brain may be stuck on the 'oohhh, shiney!' aspect of the .Net Core evolution, which is why I'm looking at you, experts, for some much needed direction / advice.
Thanks in advance,
Apr 24, 2017 09:42 AM|Zhi Lv - MSFT|LINK
From your description, since you want to use Asp.net core, I suppose it is better to use Web API.
Please refer to the following code to learn more about Web API: