You are welcome! :) :)

The answer is: It Depends! What skills does your team have / how much new learning are they able to do? Are you intending to run the old stuff concurrently with the new stuff or is it a big bang approach? What is the problem domain? That will dictate what are the best tools for the job Are you willing to risk leading edge (which may be buggy) or do you want trailing edge (which may cause upgrade issues in the future) or do you want to play it safe (e.g. go with the next-to-latest version)? Who are your clients / customers? What will they be most comfortable using? Are there off-the-shelf packages that can do what you want which could save you a lot of development time? Stevey T wrote: recommendations on what framework and mythologies/C# version/database methods/Web UI methods, to use Do not use mythologies: they are not real!

Ah, Ford, then. Poor Arthur never quite got the hang of things... Will Rogers never met me.

. Robust Services Core | Software Techniques for Lemmings | Articles The fox knows many things, but the hedgehog knows one big thing.

This was actually pretty neat back in the wild west days of single page web apps. Standard practice at the time was to assemble 'Web 2.0' apps using a combination of jQuery, duct tape, and hope. So seeing a language + framework combo (Cappuccino and Objective-J) that would let you construct your app's UI using OSX's Interface Builder and then write your application in something other than Ecmascript 3.0 was actually a breath of fresh air, even if it seems a bit crazy now. And I still wonder if they were onto something here. I still like 280Slides better than Google Slides and PowerPoint Online now, more than a decade later. FWIW, SproutCore was another framework that aimed to do kind of the same thing but using plain JS. In some ways, it was a progenitor of things like Angular and I still like some aspects of it more than Angular and React. Heck, I would actually love a modern take on this that lets you build your UI with XCode/Interface builder, then write your code in Swift and compile it all down to WASM. I think there are tools that already let you do something similar using XAML and C# compiled to WASM.

Sounds like the guy I had for one of my classes. He was a first order prick. The purpose of the class was to build a microprocessor-based project. I only got about 90% of my project finished, so he told me he was going to fail me for the course. The angels smiled on me, he thought about it for a minute, and said "Let's go check your exam scores." I had perfect scores on the midterm and the final exam. I got a C in the class. Software Zen: delete this;

I am dismayed to find no tangible examples of its usage - nothing but casual mentions of what people did to make it work. ".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

Your Shape class should be the only abstract one. Circle and Rectangle should be complete classes that inherit Shape. There is a very good set of articles on factory patterns by @SneshPrajapati here on CodeProject, starting with Factory Patterns - Simple Factory Pattern[^].

Maybe they have a service for that. Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger