3 ms·
Interesting name choice considering they have already had a .Net 1.0. I mean I get it, I understand why they chose to make this more of a 1.0 release but for th
by BinaryIdiot 10y ago
Interesting name choice considering they have already had a .Net 1.0. I mean I get it, I understand why they chose to make this more of a 1.0 release but for those already in the .Net ecosystem it seems a little confusing to me.
- malekpour 10y agoIt could have been more confusing by bumping versions. They first tried ASP.NET 5 and ASP.NET MVC 6 and EF 7 and there was no simple migration path from older version. Now they are all Core 1.0
- recursive 10y agoExcuse me if this was already obvious, but the word "core" designates a new product line, starting from 1.0. Obviously, it's informed heavily from the old .net framework, but it's not backwards compatible with it.
- BinaryIdiot 10y agoSure it's obvious. Like I said I "get it" it's just core has always been a part of .Net just less directly referred to so my first thought was this was .Net 1.0's core until I started reading through the link. Overall I think it's a good move just a little confusing (unless I'm the only one) for those who have done .Net work before.
- lmickh 10y agoThis is just a personal view, but my first instinct when I read about product "CoolApp" and "CoolApp Core" would be to assume core is a subset of the first. Not a new and re-engineered product line. I could see why others might see .Net Core as a parallel product as opposed to a new one.