There is a page indicating what the new .Net proposal is. Platform Standard . That may be the most important. If you want something portable among the various implementations that conform to this you have to stick to it. Whatever you use and is not on this list, there are no guarantees that will work in other implementations.
Compare with ASP.Net 1.0 is not wise.
The two main advantages of .Net Core is that it runs on a variety of platforms (not just operating systems, it's actually a more open technology) and does not need anything previously installed, even allowing a modular installation of the dependencies. There are several other advantages. In addition to having new features, more modern, and better thought.
It would be complicated to make a complete list of what does not exist in. Net Core because this list is very extensive if it is in detail and it is shortening every day.
I will not even mention the differences to develop it. That's a way.
Almost everything they took was for good reason.
Far from saying that .Net Core will have everything the .Net Framework (the old one we always use). Explicitly this will not happen. But much of what does not exist today must have at some point.
What you can say is that a lot of things connected to Windows will not. As Core was made to be portable, these things were left out.
-
So you do not have Windows Forms and WPF. But it has UWP, which obviously can not be used outside of Windows. There are third party options for GUI.
-
System.Drawing is not yet available.
-
Many things that only make sense in Windows, such as Enterprise.Services. Anything that depends on P / Invoke is out, but some may have substitutes, probably more modern. COM also has limitations.
-
Traditional ASP.Net (WebForms) is not supported. But even the old MVC can not work because it depends on the traditional one. I do not know if there is any effort to change that, but I doubt it. ASP.Net Core is similar to ASP.Net MVC, but not identical and compatible.
-
Integration with HTTP servers is quite a difference and still has limitations. Although you now have a base to be better.
-
As the old Entity Framework also does not work and will not work. The new is better, but it takes a while to be complete (without the legacy of the old one).
-
WCF has a lot of limitations.
-
Reflection has some limitation as well.
-
Binary serialization is not available by default
-
There is no application domain (AppDomain ).
-
The security of the application is very simplified (this is not to say that it is insecure). There is no ( CAS ).
-
-
-
-
-
-
-
-
They took away much of what was considered obsolete. There is an official list of obsolescence .
-
There are several other things, this list is not complete.
Finally, think of .Net Core as a new technology. There are cases to continue using the traditional framework . In general it is not worth converting old applications to .Net Core, unless you have a good reason. But in most cases it is interesting to use .Net Core. It is game changing for .Net.
Responding to what is best for each project is not your job. There are more specific questions about features you'll need.
A lot of people think it is worth investing in it, in fact I have never seen a new technology have adopted as fast as this, but you should form your own opinion. Certainly there are people who think otherwise.
Just starting to do to know. Remember that everything is different. You still do not know how to use it. You will have initial difficulties. He has a different philosophy and is a little grosser. I think you're thinking right. Take one step at a time.
The .Net Framework will remain supported and will have some progress, but the focus is on .Net Core.
