3 ms·

The complaint around all the different concurrent iterations of .NET rings true to me. It used to be that you only needed "current version of .net" and then yo

The complaint around all the different concurrent iterations of .NET rings true to me. It used to be that you only needed "current version of .net" and then you just ran forward with all of the standard libaries and Visual Studio handled all of that for you and it was wonderful. Now you need to work with .NET Core and download a bunch of disjoint nuget packages to make everything work; and, then you download a specific nuget package and it requires updating all your other nuget packages, on to forever. I was tasked with transitioning some of a former company's .net 4.something code to .net core, to see if we could do it, and the transition was a shock to the system, for sure. In the past, I could choose when to engage with Nuget and which packages to work with. When I went to .net core, it seemed like anything complex that I wanted to do required yet another package - in my case, anything related to running a webserver. Working with .net definitely became more complicated post .net core. edit: for clarity and enjoying the downvotes. I'm a seasoned .net developer and used it from 2009 until 2018-2019 for desktop applications and webservices. I've used nuget packages plenty for a variety of things, including Akka.net.

tracker1 6y ago
I think a lot of the newer options are much easier... the greater flexibility of detaching most libraries from the base runtime has been useful for advancing the platform as a whole. That said, I do feel the pain, the interface changes for binding web applications are very different, and if you relied on "Enterprise" libraries harder still. I'd rather do things the "new" way, but it's more the differences that make it harder. Harder still, is when trying to google how to do X with .Net Core 3 or similar... Now that it's .Net 5, at least that should make some stuff easier, until 6 comes out at the end of the year, but that's more evolutionary. Getting search results that no longer apply is a pain. It's far less the C# language as it is the platform libraries themselves and the breaking evolution through .Net Core. I think TFA has a point that renaming .Net to something else instead of .Net Core or .Net 5 may have been a good idea. Of course, now it's Azure * instead of a couple decades ago it was * .Net (anyone remember Office .Net, Windows .Net etc in early dev/beta marketing?)
MarkSweep 6y ago
It got a lot better in .NET Core three when they stopped using Nuget packages for the core framework works. Now building and updating apps based on just the core frameworks no longer installs and restores Nuget packages. This makes it faster, simpler, and takes less space on disk. You probably still will have more Nuget packages in your ASP.NET Core project than a classic .NET Framework project would. Details about the new system: https://github.com/dotnet/designs/blob/main/accepted/2019/targeting-packs-and-runtime-packs.md https://github.com/dotnet/designs/blob/main/accepted/2019/ta...
- t-writescode 6y ago
  I'm really glad they stopped that. Adding, I think it was Owin (part of the .net core framework), and then being required to update to a new version of the ... collections api? it's been a while, clearly, was one of my "... seriously?" moments when working with migrating to .net core last.
jbjbjbjb 6y ago
The author comes from the beginners perspective but it sucks for veterans too. How many transitions have you done? As a long time dotnet developer I feel like there’s been constant transitioning and back and forth. It isn’t simple to transition either. As you have to wait for all your dependencies to transition, there are usually many different solutions to update, there are breaking changes and bugs to deal with and on top of it there’s the constant moving target to be up to date. It’s definitely made it painful to use dotnet.

tracker1 6y ago

I think a lot of the newer options are much easier... the greater flexibility of detaching most libraries from the base runtime has been useful for advancing the platform as a whole. That said, I do feel the pain, the interface changes for binding web applications are very different, and if you relied on "Enterprise" libraries harder still. I'd rather do things the "new" way, but it's more the differences that make it harder. Harder still, is when trying to google how to do X with .Net Core 3 or similar... Now that it's .Net 5, at least that should make some stuff easier, until 6 comes out at the end of the year, but that's more evolutionary. Getting search results that no longer apply is a pain. It's far less the C# language as it is the platform libraries themselves and the breaking evolution through .Net Core. I think TFA has a point that renaming .Net to something else instead of .Net Core or .Net 5 may have been a good idea. Of course, now it's Azure * instead of a couple decades ago it was * .Net (anyone remember Office .Net, Windows .Net etc in early dev/beta marketing?)

MarkSweep 6y ago

It got a lot better in .NET Core three when they stopped using Nuget packages for the core framework works. Now building and updating apps based on just the core frameworks no longer installs and restores Nuget packages. This makes it faster, simpler, and takes less space on disk. You probably still will have more Nuget packages in your ASP.NET Core project than a classic .NET Framework project would. Details about the new system: https://github.com/dotnet/designs/blob/main/accepted/2019/targeting-packs-and-runtime-packs.md https://github.com/dotnet/designs/blob/main/accepted/2019/ta...

t-writescode 6y ago
I'm really glad they stopped that. Adding, I think it was Owin (part of the .net core framework), and then being required to update to a new version of the ... collections api? it's been a while, clearly, was one of my "... seriously?" moments when working with migrating to .net core last.

jbjbjbjb 6y ago

The author comes from the beginners perspective but it sucks for veterans too. How many transitions have you done? As a long time dotnet developer I feel like there’s been constant transitioning and back and forth. It isn’t simple to transition either. As you have to wait for all your dependencies to transition, there are usually many different solutions to update, there are breaking changes and bugs to deal with and on top of it there’s the constant moving target to be up to date. It’s definitely made it painful to use dotnet.