it started using mono, but some of the configuration window did not function, so.. not an immediate success.
On Sat, Feb 25, 2023 at 4:14 PM Stephen Adolph <[email protected]> wrote: > thanks, I may just try it and see.. > > > On Sat, Feb 25, 2023 at 3:37 PM <[email protected]> wrote: > >> Mono is the .NET framework ported to Linux/Mac. It lets you run the same >> .NET code on those platforms. Like any other cross platform framework there >> are bound to be a few little things that work a bit different, etc. >> >> >> >> Jeff Birt >> >> >> >> *From:* M100 <[email protected]> *On Behalf Of *Stephen >> Adolph >> *Sent:* Saturday, February 25, 2023 2:30 PM >> *To:* [email protected] >> *Subject:* Re: [M100] which .NET version should I use >> >> >> >> Jeff. what I have would only run on PC. I thought "Mono" (of which I >> know nothing, except that LaddieAlpha uses it for cross platform) might be >> a better way to go. >> >> Any suggestions? >> >> thanks. >> >> Steve >> >> >> >> >> >> On Sat, Feb 25, 2023 at 3:26 PM <[email protected]> wrote: >> >> ‘Move to Mono’? I don’t understand the question as the point of Mono is >> to run .NET aps on Linux/Mac. You are still writing .NET code. >> >> >> >> Jeff Birt >> >> >> >> *From:* M100 <[email protected]> *On Behalf Of *Stephen >> Adolph >> *Sent:* Saturday, February 25, 2023 2:07 PM >> *To:* [email protected] >> *Subject:* Re: [M100] which .NET version should I use >> >> >> >> I don't really "know" this program. I just hacked what I could >> understand to make it speak M100. >> >> >> >> Ok, well, we shall see. >> >> >> >> Would it be better to try and move this to Mono? >> >> >> >> I know that this program uses a lot of "windowy" functionality. Menus, >> buttons, etc. >> >> >> >> On Sat, Feb 25, 2023 at 2:46 PM John R. Hogerhuis <[email protected]> >> wrote: >> >> I tend to use whatever compiler I have on my computer that works with >> 4.5+ ish (I think). But I wouldn't try to hard to find an old compiler or >> move to an older framework. Most of this stuff is a free download. >> >> >> >> Maximize the number of people that can compile my version without trouble >> or recreating the project files. >> >> >> >> I don't need new features for console apps. And if they eventually break >> something it will probably be serial stuff I need that few app devs use. >> >> >> >> If you're using newer features, frameworks and libraries that's a >> different story. >> >> >> >> -- John >> >> On Sat, Feb 25, 2023, 11:22 AM Stephen Adolph <[email protected]> >> wrote: >> >> won't that impact backwards compatibility? I was thinking compile it >> with an early .NET. >> >> >> >> On Sat, Feb 25, 2023 at 1:45 PM Gary Weber <[email protected]> wrote: >> >> A lot of my Windows development has been "stuck in the past" on earlier >> versions of .NET like 4.0. >> The problem with that is it's so far out of Microsoft's support window >> that you can run into bugs or limitations that will never be fixed. >> I'd recommend going with an "LTS" version at least, like 6.0. >> >> >> >> On Sat, Feb 25, 2023 at 11:27 AM Stephen Adolph <[email protected]> >> wrote: >> >> looking for feedback. >> >> I have a pretty good prototype now of the MVT100 emulator for running on >> a windows PC. >> >> I have to pick a .NET framework to compile on. >> >> Which should I use? any suggestions? >> >> >> >> thanks >> >> Steve >> >> >> >>
