The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
We're doing something similar - going from ASP.Net Web Forms to MVC5.
Even though our apps will be "on the cloud*, we are sticking with .Net Framework. Web apps don't need to be "cross-platform", IMHO, especially in an all-Windows shop.
Even if we do switch over to core in the future, it should be fairly easy to do - if you believe Microsoft's propaganda...
".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
When you say "Standard Framework" are you referring to .NET Standard (the common denominator between .NET, .NET Core, Mono and Xamarin) or do you mean "the standard .NET that we've known for nearly two decades"?
If you're talking about .NET Standard, it's not a runtime so you can't write an application in it, only libraries.
In that case you clearly need .NET Core with perhaps .NET Standard libraries.
If you're talking about good old .NET, I'd still recommend .NET Core.
Personally, I've found moving from .NET to .NET Core very intuitive.
Dependency Injection comes out of the box, configuration files work with standard JSON (which allows nesting) and can be easily (strong typed) injected into your application.
Entity Framework Core has most of the regular EF and I've found it pretty easy to work with (code first).
If you're going for some basic CRUD stuff Razor Pages are fairly easy and intuitive without all the boiler plate of MVC.
If you're going for MVC I think they streamlined it a bit. No more Controller and ApiController, just one Controller and (JSON) API or HTML, it doesn't really matter anymore.
Considering Microsoft is continuing development for .NET Core and not the .NET Framework, it's a clear winner for me, .NET Core!
The great thing about starting new code in Core is... You don't have to make every. single. google search for dotNET information using negated keywords at the end (like me): web api auth -Core -Membership
P.S. Microsoft evidently hates developers when they name things:
• nuget packages.core (old-meaning of core libraries)
Among the differences:
- Silverlight was proprietary while webassembly (wasm) is open source.
- Silverlight was not supported by all major browsers, wasm is.
- Portions of Silverlight still live on in other technologies, and work in harmony with wasm.
And you provided a supposed quote with no context.
All that together pretty much makes your response worthless.
Yes, apparently it's bean brewing for a while now.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
I'll definitely download it and watch it for free go see it in the theater...
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain