4 ms·

Really? Because stuff like silverlight, linq_to_sql, razor/mvc and others might want a word. I know technology moves forward, by typically it does so in a much

Really? Because stuff like silverlight, linq_to_sql, razor/mvc and others might want a word. I know technology moves forward, by typically it does so in a much less costly manner, because in the real world, moving people from asp.net classic to .net core costs money. I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0.

GordonS 8y ago
> silverlight Hah, I forgot about Silverlight - mainly because I never used it (did anyone?) > razor/mvc Eh? Razor is very much still alive, and MVC lives on as ASP.NET Core MVC. > because in the real world, moving people from asp.net classic to .net core costs money. Yes, I live in the same world, and have migrated several projects from .NET to .NET Core. If you were an early adopter, it could admittedly be a bit painful, but everything "just works" now. > I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0. Really not sure what you mean here, and I can only guess that you've been thrown by Microsoft randomly releasing new .NET Core versions before the corresponding .NET Standard versions - releasing the implementation before the API. I don't like this myself, but it hardly means that .NET Standard has "came and went". Also, just a couple of weeks ago, Microsoft said ".NET Core 3.0 as well as upcoming versions of Xamarin, Mono, and Unity will be updated to implement .NET Standard 2.1"[1]. [1] https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcing-net-standard-2-1/ https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcin...
- eksemplar 8y ago
  .net core 3.0 will be .net core only. Which may not be much of a problem if you were already running it in a non-windows environment, but it’ll make it useless for those of us who also have hundreds legacy systems, and those legacy systems are the main reason we still use .net at all.
  - GordonS 8y ago
    I don't know where you are getting that from, and the link I posted plainly says otherwise - could you share your source?
    - jaxelr 8y ago
      Heres the announcement: https://github.com/aspnet/AspNetCore/issues/3753 https://github.com/aspnet/AspNetCore/issues/3753
      - GordonS 8y ago
        OK, so this announcement is not about .NET Core 3.0 not conforming to .NET Standard - it's about ASP.NET Core 3.0 only running on .NET Core, and not on .NET Standard. I agree that's still terrible news though, and I'm not sure how I managed to miss it. This seems like a very bad idea.

GordonS 8y ago

> silverlight Hah, I forgot about Silverlight - mainly because I never used it (did anyone?) > razor/mvc Eh? Razor is very much still alive, and MVC lives on as ASP.NET Core MVC. > because in the real world, moving people from asp.net classic to .net core costs money. Yes, I live in the same world, and have migrated several projects from .NET to .NET Core. If you were an early adopter, it could admittedly be a bit painful, but everything "just works" now. > I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0. Really not sure what you mean here, and I can only guess that you've been thrown by Microsoft randomly releasing new .NET Core versions before the corresponding .NET Standard versions - releasing the implementation before the API. I don't like this myself, but it hardly means that .NET Standard has "came and went". Also, just a couple of weeks ago, Microsoft said ".NET Core 3.0 as well as upcoming versions of Xamarin, Mono, and Unity will be updated to implement .NET Standard 2.1"[1]. [1] https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcing-net-standard-2-1/ https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcin...

eksemplar 8y ago
.net core 3.0 will be .net core only. Which may not be much of a problem if you were already running it in a non-windows environment, but it’ll make it useless for those of us who also have hundreds legacy systems, and those legacy systems are the main reason we still use .net at all.
- GordonS 8y ago
  I don't know where you are getting that from, and the link I posted plainly says otherwise - could you share your source?
  - jaxelr 8y ago
    Heres the announcement: https://github.com/aspnet/AspNetCore/issues/3753 https://github.com/aspnet/AspNetCore/issues/3753
    - GordonS 8y ago
      OK, so this announcement is not about .NET Core 3.0 not conforming to .NET Standard - it's about ASP.NET Core 3.0 only running on .NET Core, and not on .NET Standard. I agree that's still terrible news though, and I'm not sure how I managed to miss it. This seems like a very bad idea.