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

91–100 of 183 posts

Re: .NET Core 3.0

#91

Post by mythz »

celdon25 wrote: post #74
LandR wrote: post #41

Earlier quoted context omitted.

Visual studio crashes and hangs on me multiple times a day. Rider is just solid.

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.

Re: .NET Core 3.0

#92

Post by jsingleton »

tabtab wrote: post #76
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…

Re: I would say the learning curve is pretty high If you had to rank and list the top rough spots in the transition, what would they be? Entity-Framework changes are often cited, but what else is different enough?

It depends where your starting point is. Core bundles a lot of stuff together that was previously separate or just good practice. If you are familiar with MVC / WebAPI / EF / OWIN and already doing DI / Logging etc. then it's not much of a leap.

Re: .NET Core 3.0

#93

Post by [deleted] »

jackfoxy wrote: post #80
thrower123 wrote: post #55

Earlier quoted context omitted.

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.

I work mainly in multi-project F# solutions. VS Code Ionide plug-in seems pretty solid for single project F#, but every time I've tried to use it for multi-project I run into some sort of situation that sends me back to Visual Studio. VS has had it's own F# problems. The latest Preview edition is pretty solid, with one annoying bug. Almost every time I open my big multi-project solution I need to rebuild to get Intel…

[deleted]

Re: .NET Core 3.0

#94

Post by WorldMaker »

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...

Doing a quick skim, it feels like that migration guide should still cover the basics. (I don't think there is a big developer-facing change between ASP.NET Core 2.1 and 3.0; small subtle things like the Generic Host Builder. But you should be fine using the guide here to migrate to 2.1 and you can find simple posts on the 2.1 to 3.0 changes.)

Re: .NET Core 3.0

#95

Post by Gibbon1 »

oaiey wrote: post #15
hmexx wrote: post #13

List of performance improvements is mind-boggling: https://devblogs.microsoft.com/dotnet/performance-improvemen... How could a mature standard library / frameworks have so much performance gains to be had?

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.

Re: .NET Core 3.0

#96

Post by Nelkins »

Is anybody using Blazor for anything that isn't a toy? I'm interested in using it at work but because it appears that the payload is relatively large I wouldn't want to use it for anything that wasn't internal facing.

Re: .NET Core 3.0

#97

Post by fgonzag »

atonse wrote: post #77
dragonwriter wrote: post #10

Earlier quoted context omitted.

> But rubyists would’ve loved C#. As a Rubyist, I'll admit that C# is the least bad of the C++/Java style of static OOP languages, but it was that it was always too tied to the .NET ecosystem and heavyweight enterprise tooling more than Microsoft's “supervillian role” with regard to FOSS that made it unattractive for lots of places where I would want to use Ruby. That's improved with Core, somewhat.

I was a fulltime ruby developer before I became a full-time .NET developer (usually by accident). And things like Linq, Visual Studio, and Resharper ultimately allowed me to create code that was highly organized, while never sacrificing productivity or performance. The thing I always hated most about the .NET ecosystem was having to run on Windows Server, so that's definitely a welcome change with .NET Core. But C# h…

More than windows it was the GUI centered developer tools and server setup. With powershell and the dotnet CLI things have improved massively. Now that we can just run on Linux I'm absolutely in love. I still use Java for some projects because of library dependencies (and kotlin also makes the work enojayble) but I prefer .net for Greenfield projects

Re: .NET Core 3.0

#98

Post by jsingleton »

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.

Re: .NET Core 3.0

#99

Post by strangecasts »

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…

For the end user there is something to install - specifically, Docker, which is quite... hefty on Windows

Re: .NET Core 3.0

#100

Post by landr0id »

Nelkins wrote: post #96

Is anybody using Blazor for anything that isn't a toy? I'm interested in using it at work but because it appears that the payload is relatively large I wouldn't want to use it for anything that wasn't internal facing.

>it appears that the payload is relatively large

Not knowing much about Blazor, what are you referring to here? The size of the WASM blob for your own code, or does Blazor have an associated runtime that's large? And what is considered "large"?

Post reply on HN