Re: Mono on IBM i - Porting Mono to AIX and IBM i

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

So, to kind of lay out the track for a traditional IBM i shop, the 
sequence of events goes something like this:

1. Determine if Mono provides any potential benefit
2. Identify a zero-cost entry point
3. Find an existing projects that can be adapted as proof of concept
4. Implement proof of concept
5. Identify required infrastructure (source control, change management)
6. Identify minimum footprint for development
7. Present to management

It looks like 1 and 2 are covered. Going through your list someone ought 
to be able to find a candidate for steps 3 and 4.  And in fact, a formal 
list like that would seem to be a great thing to have in a Wiki 
somewhere to help with the uptake.  Steps 5 and 6  are the nitty gritty 
stuff of what would it take to get this cool widget into production to 
be maintained and modified along with the rest of my application software.

This is a lot of what I'm currently doing with my series in implementing 
Linux in a VM.  In fact, if I were able to get enough time to do 
something like this, I think it would be good for a few articles!

On 4/18/2019 7:39 AM, Richard Schoen wrote:
> Visual Studio Community
> https://visualstudio.microsoft.com/vs/community/
>
> Oh, and by the way VS 2019 now has built-in full IDE support for Node and Python development and real-time debugging as well.
>
> Damn that's cool !!
>
> And, of course there's VS code, but that's more for text editing.