2 ms·
Too early for .Net Core. Not ready. RoR is what you want. If you have to learn RoR still then maybe that changes the story. Say you know C# and not Ruby- then y
by BuckRogers 10y ago
Too early for .Net Core. Not ready. RoR is what you want. If you have to learn RoR still then maybe that changes the story. Say you know C# and not Ruby- then you could just build your backend on standard .Net and move to .Net Core when it makes sense.
- patates 10y agoThat made sense to me and after a web search, found a blog post in MSDN[1] which summarizes the API compatibility situation. [1]: https://blogs.msdn.microsoft.com/dotnet/2016/02/10/porting-to-net-core/ https://blogs.msdn.microsoft.com/dotnet/2016/02/10/porting-t...