We have as much .NET legacy as we do COBOL legacy. Our .NET developers are experts with 15-20 years of experience in our shop. They really want to move to .NET Core. They tried to move to .NET Core earlier, but they stopped because .NET Core did not support the way they were connecting to the IBM i. Maybe I didn't describe the reasons accurately. I thought it was because ADO.NET is no longer supported in .NET Core-but I am not a .NET expert.
The bottom line for me is: our .NET developers are moving to .NET Core. Which means the browser interfaces we use to replace green screens will be in .NET Core.
If we use .NET Core, and we end up using node to create IBM i web services, it just seems natural to me to explore the JavaScript Services in .NET Core.
Thanks,
Kelly Cookson
IT Project Leader
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<
http://www.dotfoods.com>
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Tuesday, April 10, 2018 8:04 AM
To: web400@xxxxxxxxxxxx
Subject: [EXTERNAL] Re: [WEB400] ibm_db node module and IBM Data Server Driver
Also, they don't really need .Net Core to start building .Net web services to IBMi. The standard .Net components still work fine with the ADO.Net Database Drivers and ODBC.
At the moment there is no super-compelling reason to switch to .Net Core unless you want to do multi-platform hosting, which is my interest in it.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx<mailto:richard.schoen@xxxxxxxxxxxxxxx>
p. 952.486.6802
w. helpsystems.com
-----Original Message-----
message: 5
date: Tue, 10 Apr 2018 12:55:29 +0000
from: Tim Fathers <X700-IX2J@xxxxxxxxxxx<mailto:X700-IX2J@xxxxxxxxxxx>>
subject: Re: [WEB400] ibm_db node module and IBM Data Server Driver
But we've started to gradually replace green screen development with .NET web front-ends.
...so where does Angular/React fit in here? I'm a tad confused (as usual!) about the mix of .NET and the JS frameworks for the front-end. Especially in the light of this sentence...
If we adopt node, then we could also take advantage of .NET Core JavaScript Services, which allows .NET apps to incorporate node modules and custom JavaScript functions running on node on windows.
...which seems to imply .NET on the server side?
In any case, I think my advice would remain the same - make your existing backend application available as a web service. If you have .NET developers writing fat clients then I would refactor these so that they no longer communicate with the IBM i via ADO but using web service calls too, this gives you many advantages, not least of which means that you can use exactly the same web services to write web applications as you can to write your .NET clients.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx<mailto:WEB400@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/web400<
https://lists.midrange.com/mailman/listinfo/web400>
or email: WEB400-request@xxxxxxxxxxxx<mailto:WEB400-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/web400<
https://archive.midrange.com/web400>.
midrange.com
