5 ms·

> how do people even keep up with these rapid changes in the post Core world and what/when to use them? You wished that the dev world moved slower. Sorry, thi

> how do people even keep up with these rapid changes in the post Core world and what/when to use them? You wished that the dev world moved slower. Sorry, things move fast nowadays. The .NET team decided to stay relevant, by moving fast to keep up. That's just how it is.

alkonaut 6y ago
As a desktop developer I really miss the Big Bang releases and slow pace yes. We are doing a 2-year transition between 4.7.1 and 4.7.2 now! What goes on beyond that is just a fog. Some of our third party dependencies are probably never going to be ported core while many others are starting to lose maintenance on netfx. Being in the position of having to maintain a netfx desktop app for the coming 10-20 years is looking bleak.
- SideburnsOfDoom 6y ago
  Then stay on the LTS releases. They come roughly annually.
  - svick 6y ago
    Starting with .Net 5, there will be one major release exactly once a year, and one LTS release exactly once every two years. (see https://devblogs.microsoft.com/dotnet/introducing-net-5/ https://devblogs.microsoft.com/dotnet/introducing-net-5/)
    - alkonaut 6y ago
      .NET 5 is a no go for those of us who are stuck on netfx. There is no compatibility.
      - SideburnsOfDoom 6y ago
        > There is no compatibility That's not true.
        alkonaut 6y ago
        I mean for existing pre-built binary libraries built for netfx (which is what we are stuck with as dependencies in many cases) there is no way to use them under core/net5 that I’m aware of (I’d be happy to learn that it was!). E.g I have a huge library from Autodesk that targets 4.6.2 and I consume it from 4.7.1 now. I don’t think they have a plan to support a Core/net5 framework so my app can’t either. Obviously you can rebuild libraries and target both/netstandard/whatever but that’s not what I mean.
        SideburnsOfDoom 6y ago
        Seems to me more like the issue is with Autodesk and with an unmaintained binary dependency, not with .NET at all.
        ptx 6y ago
        There is actually a compatibility mode[1], although not everything is supported: "Starting with .NET Standard 2.0, the .NET Framework compatibility mode was introduced. This compatibility mode allows .NET Standard and .NET Core projects to reference .NET Framework libraries. Referencing .NET Framework libraries doesn't work for all projects, such as if the library uses Windows Presentation Foundation (WPF) APIs, but it does unblock many porting scenarios." I don't know if there are downsides or if the compatibility will be removed in the future. https://docs.microsoft.com/en-us/dotnet/core/porting/third-party-deps#net-framework-compatibility-mode https://docs.microsoft.com/en-us/dotnet/core/porting/third-p...
  - alkonaut 6y ago
    The problem isn’t the framework so much as libraries and their dependencies. A required update to one library might require a bump in a second library and that library drops netfx support and supports only core/net5 in that bumped version. Stuck between a rock and a hard place.

alkonaut 6y ago

As a desktop developer I really miss the Big Bang releases and slow pace yes. We are doing a 2-year transition between 4.7.1 and 4.7.2 now! What goes on beyond that is just a fog. Some of our third party dependencies are probably never going to be ported core while many others are starting to lose maintenance on netfx. Being in the position of having to maintain a netfx desktop app for the coming 10-20 years is looking bleak.

SideburnsOfDoom 6y ago
Then stay on the LTS releases. They come roughly annually.
- svick 6y ago
  Starting with .Net 5, there will be one major release exactly once a year, and one LTS release exactly once every two years. (see https://devblogs.microsoft.com/dotnet/introducing-net-5/ https://devblogs.microsoft.com/dotnet/introducing-net-5/)
  - alkonaut 6y ago
    .NET 5 is a no go for those of us who are stuck on netfx. There is no compatibility.
    - SideburnsOfDoom 6y ago
      > There is no compatibility That's not true.
      - alkonaut 6y ago
        I mean for existing pre-built binary libraries built for netfx (which is what we are stuck with as dependencies in many cases) there is no way to use them under core/net5 that I’m aware of (I’d be happy to learn that it was!). E.g I have a huge library from Autodesk that targets 4.6.2 and I consume it from 4.7.1 now. I don’t think they have a plan to support a Core/net5 framework so my app can’t either. Obviously you can rebuild libraries and target both/netstandard/whatever but that’s not what I mean.
        SideburnsOfDoom 6y ago
        Seems to me more like the issue is with Autodesk and with an unmaintained binary dependency, not with .NET at all.
        ptx 6y ago
        There is actually a compatibility mode[1], although not everything is supported: "Starting with .NET Standard 2.0, the .NET Framework compatibility mode was introduced. This compatibility mode allows .NET Standard and .NET Core projects to reference .NET Framework libraries. Referencing .NET Framework libraries doesn't work for all projects, such as if the library uses Windows Presentation Foundation (WPF) APIs, but it does unblock many porting scenarios." I don't know if there are downsides or if the compatibility will be removed in the future. https://docs.microsoft.com/en-us/dotnet/core/porting/third-party-deps#net-framework-compatibility-mode https://docs.microsoft.com/en-us/dotnet/core/porting/third-p...
- alkonaut 6y ago
  The problem isn’t the framework so much as libraries and their dependencies. A required update to one library might require a bump in a second library and that library drops netfx support and supports only core/net5 in that bumped version. Stuck between a rock and a hard place.