Ef7
EF7 is a rewrite that does not yet have all the features of EF6 - so you probably wonβt want to switch to it at this point unless you really need one of its new features.
EF7 itself is independent of ASP.NET, you can use it for any .NET application. The design documents for EF7 indicate that it will support .NET 4.5.1, since your application targets this version or later, you can use EF7.
From the Microsoft project document has this to say about EF7:
- EF7 is a burst release. When there is a better template / API / etc. we accept changes (unless there are benefits three times).
- EF7 will not replace EF6 on RTM 7.0.0 day.
- EF6 will continue to be the best choice for many applications for some time to come.
- We are not going to push people to upgrade by supporting the existing application on EF6 and supporting it.
- Moving from EF6 to EF7 is not an upgrade scenario, it is a port scenario.
- EF7 is not a reimplementation of EF6 (EF7 has simpler display capabilities, EDM, etc.).
SignalR and Identity
According to Scott Hanselman's blog post , it looks like the ASP.NET 4.X branch will continue for some time, and indeed changing the naming convention actually opens up the possibility of even switching to ASP.NET 5.X if necessary.
Microsoft has been supporting WebForms for a long time, so even if SignalR 3 and Identity 3 are only available for Core 1.0, I still expect to see new features added in the version of compatible with ASP.NET 4.X (just as it was in case of adding new features in ASP.NET MVC, as well as WebForms). This is just my opinion, although I cannot find design documents for SignalR 3, which makes me wonder, not at this point.
tomRedox
source share