Just from the examples on this list, it sounds like the only winning move is not to play.
I have a handful of sites running ASP.NET 4.5. Migrating them would cost an unknown amount of time and require substantial rewriting of major components (such as all data access). It might not even be physically possible to do, given dependencies on libraries that are still 4.5 only.
It sounds like it would also kill our build process dead (adding another major rewrite to the tally). And of course, it would leave us reliant (correct me if I'm wrong here) on a lighter weight version of VS.NET so we'd roll back the clock about 10 years on ReSharper-like goodness.
As reward for this, migrating over to Core would gain me roughly $0 in business value.
The alternate course is to stay with 4.5 for as long as possible, eventually moving across when Microsoft decide to VB6 it.
Glad to hear. I hadn't seen them mention it anywhere, and since it was such an obvious dealbreaker, I would have expected it to be a major talking point.
I feel like you're conflating .NET Core and ASP.NET Core. You can use ASP.NET Core 1.0 on .NET 4.6.x today. If you don't need cross-plat, that's cool. But you have the full API surface area you have today, plus some significant new features and perf improvements.
on a lighter weight version of VS.NET so we'd roll back the clock about 10 years on ReSharper-like goodness.
I've been using Rider from JetBrains on and off for a few months. I'd recommend it. It's great to just remove MS from the picture and come that much closer to using IntelliJ in my Windows-based job.
Comments
Just from the examples on this list, it sounds like the only winning move is not to play.
I have a handful of sites running ASP.NET 4.5. Migrating them would cost an unknown amount of time and require substantial rewriting of major components (such as all data access). It might not even be physically possible to do, given dependencies on libraries that are still 4.5 only.
It sounds like it would also kill our build process dead (adding another major rewrite to the tally). And of course, it would leave us reliant (correct me if I'm wrong here) on a lighter weight version of VS.NET so we'd roll back the clock about 10 years on ReSharper-like goodness.
As reward for this, migrating over to Core would gain me roughly $0 in business value.
The alternate course is to stay with 4.5 for as long as possible, eventually moving across when Microsoft decide to VB6 it.
Sounds like a plan.
I'm tracking the dependencies of libraries at: https://anclafs.com (ASP.NET Core Library and Framework Support)
Prefix is on there so I'll update it to support .NET Core in addition to the ASP.NET Core it already supported (on .NET 4.5).
Migrating anything big is probably a bad idea but for new projects Core might be a good option.
No, you can just use the normal Visual Studio, with ReSharper support.
Glad to hear. I hadn't seen them mention it anywhere, and since it was such an obvious dealbreaker, I would have expected it to be a major talking point.
Yep, Resharper is fine but NCrunch won't work for any projects targeting Core, however.
...and that is a dealbreaker.
I feel like you're conflating .NET Core and ASP.NET Core. You can use ASP.NET Core 1.0 on .NET 4.6.x today. If you don't need cross-plat, that's cool. But you have the full API surface area you have today, plus some significant new features and perf improvements.
I've been using Rider from JetBrains on and off for a few months. I'd recommend it. It's great to just remove MS from the picture and come that much closer to using IntelliJ in my Windows-based job.
So why would you do it in the first place? Because "It's the Future"?