Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET Core 3.0

devblogs.microsoft.com

Post reply on HN
Print view View original

111–120 of 183 posts

Re: .NET Core 3.0

#111

Post by Gibbon1 »

mgkimsal wrote: post #51
Dude2029 wrote: post #38

Earlier quoted context omitted.

Break the bubble, talk to more C# devs from different kinds of businesses.

Often, you have to make a serious effort, and that goes for all sides. "talk to more C# devs from different kinds of businesses" As a PHP dev who's done C#, Java, Perl, CF, VB and more... I'd rarely find any other PHP devs at our local MS and Java user groups. In a few cases, I was the first "PHP developer" some of these people had ever met. Java/C# tend to be used in larger enterprises, and they tend to be used by p…

Friend of mine mentioned their boyfriend is a corporate dev who programs in C#. Guy doesn't seem to mind that the work is boring and repetitive. Just he gets paid well, doesn't work too hard. Gets 6 weeks of vacation. Which is helpful because his mom and cousins all live in China. And his coworkers aren't a bunch of assholes. (If you're too much of an asshole where he works the boss pushes a button and you get managed out)

Re: .NET Core 3.0

#112

Post by interlocutor »

nitePhyyre wrote: post #107
rajeev-k wrote: post #79

Earlier quoted context omitted.

Docker is a better way to distribute apps than Electron, in my opinion. From a developer point of view you just build a regular web app, so better than Electron. From the user's point of view, Docker is better because of isolation, and because there is nothing to install. You run just one command to download and run the image. If you want the app to have its own window then use Chrome's "Create shortcut" command. Thi…

"From the user's point of view, Docker is better [...] run just one command" Nope. Your "better" solution just became fundamentally impossible for 99.9% of users.

See https://kitematic.com/ it is a UI for starting containers.

Re: .NET Core 3.0

#113

Post by manigandham »

jsingleton wrote: post #98
avgDev wrote: post #23

I have been developing in .Net MVC 5 and now the last 6 months in .Net Core 2.1. Core is pretty awesome, I would say the learning curve is pretty high, but I'm very satisfied. Previously, I used Java in school. The .Net stack offers a lot of jobs in enterprise companies, if you are someone that dislikes SV mindset. Also, Visual Studio is an insane IDE. Although, I recently did have some nasty bugs but updates are com…

It's usually a good idea to wait for the patch release before updating. This applies to most software, including VS, VSC and .NET Core. Being an early adopter sucks unless you're just testing it out. If it's your job then wait for it to stabilise and for the real-world bug fixes. The next Long Term Support version of .NET Core will be 3.1. It should be out in November.

.Net 3.0 has gone through about a dozen preview releases and the last 4 have a go-live production license. It's much better tested than the old .NET Framework with its monolithic releases.

Re: .NET Core 3.0

#114

Post by pathartl »

DenisM wrote: post #40

The only way to get C# 8 is to move to .NET Core, I can't really avoid this anymore. And for me it means moving to ASP.NET Core... Anyone recently migrated projects from ASP.NET MVC to ASP.NET Core? I hope there is a gradual way, like this: https://www.hackernoon.com/how-to-migrate-project-from-aspne...

Not migrated, but we do a lot of CRUD based applications for clients and have a small dev team so it feels like we're kinda porting it over.

The largest change is dependency injection and Entity Framework. DI is insanely better and just more intuitive. EF is really a move from EF to EF Core which has quite a few differences that can introduce some road bumps.

In my opinion, I've gained the most from moving from HTML helpers in Razor to Tag Helpers. It's basically just components for Razor, but it allows us to make a really nice UI library and cuts down on so much of our markup without having to write a bunch of overloads for the same helper.

As far as MVC vs. Razor Pages, I'm still not in love with Pages. It feels a bit too much like ASP.NET Web Forms did. I still use MVC practices and it's almost the same exact experience. AJAX forms are a bit better this time around, but I'm really waiting until Blazor becomes more viable before I make a jump like that.

Re: .NET Core 3.0

#115

Post by TurboHaskal »

DavidWoof wrote: post #82
gtsteve wrote: post #25

Earlier quoted context omitted.

VS is very good but I've been using Rider since the start of this year for most work, I found it to be a very strong competitor.

I've been Rider almost exclusively for about 2 years now, ever since I've been coding Core. VS is fine, but VS w/Resharper is a dog. With Rider, R# is a first class citizen, which makes a huge difference. Not to mention that the vim emulation and other addons are solid due to being shared with the intellij suite of apps.

Rider blows Visual Studio out of the water for anything F# as well. It is really a shame that Microsoft no longer seems to care about it.

Re: .NET Core 3.0

#116

Post by manigandham »

thrower123 wrote: post #55
dmix wrote: post #49

Earlier quoted context omitted.

It's great to see the enterprise world catching up with the tech world

I fail to see what the point of trying to use VS Code for .NET development would be. I suppose if you like tying one hand behind your back and making things more difficult for yourself for some reason. Or maybe you like cobbling together a rickety pile of plugins. If cost is a concern, there's Rider or even MonoDevelop.

OmniSharp is the official C# plugin and all you need for .NET projects, and it's usually installed by default. VS Code starts faster, runs lighter, and provides 80% of the functionality of VS for most major products, and it's getting better every release. I find it more productive than VS for typical web projects.

Re: .NET Core 3.0

#117

Post by celdon25 »

mythz wrote: post #91
celdon25 wrote: post #74

Earlier quoted context omitted.

I try to avoid anything by Jetbrains, as the process of reporting bugs and trying to get show-stopping bugs fixed has been a nightmare with them. This was during their RC phase of Rider, where I had a number of bugs. They went ahead and shipped it to full release (where it was no longer free of charge) without fixing a single one of the bugs I reported and even followed up on. What is the point of an RC beta test if…

That’s about the opposite experience that I’ve had, they’ve always been quick to respond and resolve my reported issues, they’ve even created tickets themselves when I’ve reported them over Twitter.

This bug has been open for 3 years (and not touched for 2 years). It's stuff like this you see everywhere: https://youtrack.jetbrains.com/issue/RIDER-3461

Re: .NET Core 3.0

#118

Post by gameswithgo »

Gibbon1 wrote: post #95
oaiey wrote: post #15

Earlier quoted context omitted.

Well, in the traditional desktop space performance was not that critical as it is with cloud deployments. Also hardware intrinsics are a new toy they have available.

Seems to me it was fast enough on the desktop and uniformly responsive to events. If you wanted a Windows CRUD desktop application, really nothing better. I suspect that the CLI and the JVM are about as fast, about 2 to 10 times slower than C++. But that .nets libraries are more performant.

.NET started to barely surpass JVM with .NET Core 2, of course this is just a general tendency, actual performance depends greatly on the problem domain, how cleverly program, what counts as "java" and "c#" and so on.

Re: .NET Core 3.0

#119

Post by thomasz »

jsingleton wrote: post #98
avgDev wrote: post #23

I have been developing in .Net MVC 5 and now the last 6 months in .Net Core 2.1. Core is pretty awesome, I would say the learning curve is pretty high, but I'm very satisfied. Previously, I used Java in school. The .Net stack offers a lot of jobs in enterprise companies, if you are someone that dislikes SV mindset. Also, Visual Studio is an insane IDE. Although, I recently did have some nasty bugs but updates are com…

It's usually a good idea to wait for the patch release before updating. This applies to most software, including VS, VSC and .NET Core. Being an early adopter sucks unless you're just testing it out. If it's your job then wait for it to stabilise and for the real-world bug fixes. The next Long Term Support version of .NET Core will be 3.1. It should be out in November.

That's very much true for tools like Visual Studio, but not for the runtime itself.

Re: .NET Core 3.0

#120

Post by cpitman »

rajeev-k wrote: post #79
strangecasts wrote: post #65

Earlier quoted context omitted.

Yes - while WPF and Windows Forms are still Windows-exclusive, there are several cross-platform UI libraries for .NET Core, like Eto.Forms ( https://github.com/picoe/Eto ) and Avalonia ( https://avaloniaui.net/ ). It's also possible to build an Electron wrapper around an ASP.NET Core web app: https://github.com/ElectronNET/Electron.NET

Docker is a better way to distribute apps than Electron, in my opinion. From a developer point of view you just build a regular web app, so better than Electron. From the user's point of view, Docker is better because of isolation, and because there is nothing to install. You run just one command to download and run the image. If you want the app to have its own window then use Chrome's "Create shortcut" command. Thi…

A basic requirement for distributing desktop apps should be not requiring root to install/run them.
Post reply on HN