4 ms·

I've tried to port a MVC project to .NETCore 2 a while ago, it was pretty painful mainly due to lack of @helper syntax in views (everything which relied to @hel

I've tried to port a MVC project to .NETCore 2 a while ago, it was pretty painful mainly due to lack of @helper syntax in views (everything which relied to @helper had to be changed). Also, from what i saw, nobody is actually in a rush to "move" to .NETCore, most big shops still rely on .Net Framerwork , i still do some occasional work on a project which is using .Net Remoting :)

manigandham 7y ago
I find the opposite to be true. Many companies are moving to .NET Core, especially the independent dev shops. Cross-platform, easier to develop, faster and cheaper to run, and now supports desktop APIs.
EnderMB 7y ago
There are some similarities to Python 3 in .NET Core adoption. I know plenty of people that would love nothing more than to be up to date and to start using .NET Core, but many of them rely on certain libraries that simply aren't there yet. I know a load of Umbraco devs that are eager to make the jump, but until their CMS supports it, they're kinda stuck if it's a dependency.
- sebazzz 7y ago
  Many libs already support it. But the end-users, the web applications, are the problem. If you haven't properly separated business logic from UI, which might very well be the case if your project budgets aren't too high or other causes, you will have a rewrite on your hands instead of a port. A rewrite which is, especially on low budgets, not worth it.
- oaiey 7y ago
  Just with the difference, that there is not 2/3 culture split here. Everyone agrees that .NET Core is the future and should be used. The universal cloud adoption (e.g. AWS Lambda), containerization and Linux deployments are so huge selling points for .NET Core. People are hold back because of deprecated tech and because no one touches a running system without need. And maybe that black matter developers just do not know yet ;).
  - EnderMB 7y ago
    For reference, I'm mostly talking about brand-new projects, and purely from my perspective as a former .NET dev that still spends time with the local .NET community. I've not met a single .NET dev that doesn't want to use .NET Core. Hell, if anything, a lot of them would love the opportunity to use .NET on a Unix system, and to use established tooling not available on Windows. The problem is that the tools they use aren't ported yet. Umbraco is a key example, as the most popular .NET CMS in use today. It's a great CMS, but we're at least 1-2 years away from a .NET Core implementation, and probably even longer if we're hoping for a first-class Postgres/MySQL backed implementation. Until then, as you've rightly said, there's no need to switch to .NET Core.
    - scarface74 7y ago
      I don’t care about being able to develop .Net apps on Linux. Being able to deploy to Linux is a game changer especially in the cloud. Anytime that you add Windows to a cloud environment you get hit with the triple whammy of slow startup times, increased licensing costs and increased resource requirements.
mirekrusin 7y ago
I think this news marks the point from which we may see the move happening.
- WorldMaker 7y ago
  The marketing move of stopping .NET Framework at 4.x, and branding the next version of Core to just .NET 5 with no "Core" in sight will probably also push a lot more companies to move ahead with the migration (if for no other reason than the silly baseline that 5 > 4 and what manager wants to be one behind).
asp_hornet 7y ago
In my experience, it’s the opposite. If you’re not migrating your apps to core your hiring pool is going to be getting significantly smaller and smaller over the next couple of years. Think Swift vs Objective C or old jquery heavy websites vs transpiled ES6.
Someone1234 7y ago
They're working on bringing back @helper in .Net Core 3 for back-compat: https://github.com/aspnet/AspNetCore/issues/5110 https://github.com/aspnet/AspNetCore/issues/5110

manigandham 7y ago

I find the opposite to be true. Many companies are moving to .NET Core, especially the independent dev shops. Cross-platform, easier to develop, faster and cheaper to run, and now supports desktop APIs.

EnderMB 7y ago

There are some similarities to Python 3 in .NET Core adoption. I know plenty of people that would love nothing more than to be up to date and to start using .NET Core, but many of them rely on certain libraries that simply aren't there yet. I know a load of Umbraco devs that are eager to make the jump, but until their CMS supports it, they're kinda stuck if it's a dependency.

sebazzz 7y ago
Many libs already support it. But the end-users, the web applications, are the problem. If you haven't properly separated business logic from UI, which might very well be the case if your project budgets aren't too high or other causes, you will have a rewrite on your hands instead of a port. A rewrite which is, especially on low budgets, not worth it.
oaiey 7y ago
Just with the difference, that there is not 2/3 culture split here. Everyone agrees that .NET Core is the future and should be used. The universal cloud adoption (e.g. AWS Lambda), containerization and Linux deployments are so huge selling points for .NET Core. People are hold back because of deprecated tech and because no one touches a running system without need. And maybe that black matter developers just do not know yet ;).
- EnderMB 7y ago
  For reference, I'm mostly talking about brand-new projects, and purely from my perspective as a former .NET dev that still spends time with the local .NET community. I've not met a single .NET dev that doesn't want to use .NET Core. Hell, if anything, a lot of them would love the opportunity to use .NET on a Unix system, and to use established tooling not available on Windows. The problem is that the tools they use aren't ported yet. Umbraco is a key example, as the most popular .NET CMS in use today. It's a great CMS, but we're at least 1-2 years away from a .NET Core implementation, and probably even longer if we're hoping for a first-class Postgres/MySQL backed implementation. Until then, as you've rightly said, there's no need to switch to .NET Core.
  - scarface74 7y ago
    I don’t care about being able to develop .Net apps on Linux. Being able to deploy to Linux is a game changer especially in the cloud. Anytime that you add Windows to a cloud environment you get hit with the triple whammy of slow startup times, increased licensing costs and increased resource requirements.

mirekrusin 7y ago

I think this news marks the point from which we may see the move happening.

WorldMaker 7y ago
The marketing move of stopping .NET Framework at 4.x, and branding the next version of Core to just .NET 5 with no "Core" in sight will probably also push a lot more companies to move ahead with the migration (if for no other reason than the silly baseline that 5 > 4 and what manager wants to be one behind).

asp_hornet 7y ago

In my experience, it’s the opposite. If you’re not migrating your apps to core your hiring pool is going to be getting significantly smaller and smaller over the next couple of years. Think Swift vs Objective C or old jquery heavy websites vs transpiled ES6.

Someone1234 7y ago

They're working on bringing back @helper in .Net Core 3 for back-compat: https://github.com/aspnet/AspNetCore/issues/5110 https://github.com/aspnet/AspNetCore/issues/5110