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 <twospru...@gmail.com> 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 <g...@web8201.com> 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 <twospru...@gmail.com> >> 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 >>> >>>
