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.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen.
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
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!
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
So there's this thing in .NET called the "default binder" which has methods like BindToMethod() and BindToProperty().
What it does is it tells .NET how to resolve things like overloaded methods and choose which one is appropriate based on the passed in arguments.
Reflection uses it underneath Type.InvokeMember() and the C# compiler (as well as other compilers) almost certainly use it to help with choosing what methods to bind to (on external types) within a method/property group.
The docs use words like "generally". I wish I was joking. As in generally it only does widening conversions on parameters.
I don't care about generally. I care about specifics, because I have to emulate it for my own non-compiled types.
it's off to the reference source (again)
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.