4 ms·

Looks like MS realized they made a mess with .net core ...before thinking through how they should have done this... It was really not difficult to see ..if they

by ameyv 7y ago

Looks like MS realized they made a mess with .net core ...before thinking through how they should have done this... It was really not difficult to see ..if they wanted to make .net open source and their BA, PM and developer should have seen this coming... after MS bought Xamarin..they could have worked on mono and make things easier for everybody... Now they are abandoning again this new '.Core' bandwagon...so much money and time was spend by community on creating and building libraries product... I just convinced my PM and team, that we should consider .net core and they have agreed...we have started development of our new app.. This news will make things more complicated...Sigh Edit: Quite negative votes..No need to down vote..just explain your viewpoint with more civilized means using "reply"

lwansbrough 7y ago
The differentiation of .NET Core allowed the team to leave legacy problems behind and focus on multi-platform first and foremost. Now that .NET Core has been established and has more or less reached parity with .NET Framework, there's little reason to continue promoting the latter, and thus the name "Core" is redundant because it is the only future for the .NET platform. I think it's safe to think of this not as abandoning .NET Core but conversely they're promoting the technology behind .NET Core as THE future. I would expect the migration from .NET Core 3.1 to .NET 5 to be quite straight forward.
- ameyv 7y ago
  Lets see..
paavohtl 7y ago
This announcement just means they'll call the next version of .NET Core .NET 5 and kill the original Framework for good. They are not abandoning .NET Core, just changing the branding.
UglyToad 7y ago
Unless I misunderstood the article is it not the case that this is just .NET Core 5 (we're currently on/near .NET Core 3)? This announcement sounded more like unifying the various different bits of. NET on 5 in future rather than yet another breaking change?
- ameyv 7y ago
  I hope so
- runfaster2000 7y ago
  It is both things ... basically .NET Core 5 (as you say) but also making it so that .NET Core can support all modern .NET scenarios.
dragonwriter 7y ago
> Looks like MS realized they made a mess with .net core Looks like .NET Core did exactly what it was supposed to; provide a early-usable bridge to where .NET was headed for the people who didn't have legacy compatibility requirements while the implementation hat was the future got to the point where it could subsume the role of the legacy .NET Framework. > Now they are abandoning again this new '.Core' bandwagon... No, they are abandoning the old .NET Framework, because everything needed will now be implemented in .NET Core. They are also then skipping a major version in the numbering for .NET Core (so that the version number is also greater than the last-ever .NET Framework version) and dropping the modifier “Core” from the branding because there is no longer a “.NET Framework” for core to be contrasted against.
- cwyers 7y ago
  It's very possible that MS did all of the right things here, and still did a terrible job of messaging it.
  - merb 7y ago
    actually i think .net 5 will clear a lot of stuff up. basically there is no more naming confusion and once we are on asp.net 6 no version conflicts will ever be there. its the best step they could do. they also communicate clearly now that there will only be one dotnet implementation in the future, .net 5 and forward. in the past there was no clear message what will happen with mono, .net4x, etc...
  - caspper69 7y ago
    It's also possible people have reading comprehension problems.
    - cwyers 7y ago
      Sure, but you can view things as "where do I assign blame" or "what are my fixed inputs." If you look for something to blame, maybe it's that people lack reading comprehension. If it's enough people getting confused, and it matters to you that people understand things -- even if things would be solved by them reading/understanding the right things, you need to change what you can change, because you can't change your fixed inputs (in this case, your audience).
manigandham 7y ago
This is .NET Core still. They're just dropping the "Core" word from the name since all the other frameworks (Framework, Mono, Xamarin, PCL) are now retired. If you're building with .NET Core now, you have nothing to worry about.
UK-AL 7y ago
This is just the next version .net core

by ameyv 7y ago

lwansbrough 7y ago

The differentiation of .NET Core allowed the team to leave legacy problems behind and focus on multi-platform first and foremost. Now that .NET Core has been established and has more or less reached parity with .NET Framework, there's little reason to continue promoting the latter, and thus the name "Core" is redundant because it is the only future for the .NET platform. I think it's safe to think of this not as abandoning .NET Core but conversely they're promoting the technology behind .NET Core as THE future. I would expect the migration from .NET Core 3.1 to .NET 5 to be quite straight forward.

ameyv 7y ago
Lets see..

paavohtl 7y ago

This announcement just means they'll call the next version of .NET Core .NET 5 and kill the original Framework for good. They are not abandoning .NET Core, just changing the branding.

UglyToad 7y ago

Unless I misunderstood the article is it not the case that this is just .NET Core 5 (we're currently on/near .NET Core 3)? This announcement sounded more like unifying the various different bits of. NET on 5 in future rather than yet another breaking change?

ameyv 7y ago
I hope so
runfaster2000 7y ago
It is both things ... basically .NET Core 5 (as you say) but also making it so that .NET Core can support all modern .NET scenarios.

dragonwriter 7y ago

> Looks like MS realized they made a mess with .net core Looks like .NET Core did exactly what it was supposed to; provide a early-usable bridge to where .NET was headed for the people who didn't have legacy compatibility requirements while the implementation hat was the future got to the point where it could subsume the role of the legacy .NET Framework. > Now they are abandoning again this new '.Core' bandwagon... No, they are abandoning the old .NET Framework, because everything needed will now be implemented in .NET Core. They are also then skipping a major version in the numbering for .NET Core (so that the version number is also greater than the last-ever .NET Framework version) and dropping the modifier “Core” from the branding because there is no longer a “.NET Framework” for core to be contrasted against.

cwyers 7y ago
It's very possible that MS did all of the right things here, and still did a terrible job of messaging it.
- merb 7y ago
  actually i think .net 5 will clear a lot of stuff up. basically there is no more naming confusion and once we are on asp.net 6 no version conflicts will ever be there. its the best step they could do. they also communicate clearly now that there will only be one dotnet implementation in the future, .net 5 and forward. in the past there was no clear message what will happen with mono, .net4x, etc...
- caspper69 7y ago
  It's also possible people have reading comprehension problems.
  - cwyers 7y ago
    Sure, but you can view things as "where do I assign blame" or "what are my fixed inputs." If you look for something to blame, maybe it's that people lack reading comprehension. If it's enough people getting confused, and it matters to you that people understand things -- even if things would be solved by them reading/understanding the right things, you need to change what you can change, because you can't change your fixed inputs (in this case, your audience).

manigandham 7y ago

This is .NET Core still. They're just dropping the "Core" word from the name since all the other frameworks (Framework, Mono, Xamarin, PCL) are now retired. If you're building with .NET Core now, you have nothing to worry about.

UK-AL 7y ago

This is just the next version .net core