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

.NET Core 3.0 Concludes the .NET Framework API Porting Project

github.com

Post reply on HN
Print view View original

251–260 of 317 posts

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#251

Post by WorldMaker »

noderat wrote: post #206
jeswin wrote: post #72

Earlier quoted context omitted.

> Then with static using directives, you don't need to spell out the namespaces. Static using directives! Certainly a useful tool, thank you. I had been away from the .Net universe for a while and I think I have some more catching up to do. Some of the newer changes in C# help a lot with reducing code heft, even though it makes the language more complex. However, the Framework seems to be headed in the opposite direc…

I really wish the documentation for things like DI, IOptions and ILogger were moved out of the ASP.NET documentation. Trying to decipher from the documentation how to use these in a non-ASP.NET project is needlessly complicated.

It's getting pushed out of ASP.NET with the "Generic Host" efforts. It's still for the time being in ASP.NET documentation, but you see it's moving in that direction.

https://laurentkempe.com/2019/09/03/WPF-and-dotnet-Generic-H...

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/ho...

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#252

Post by mickdaisy »

LandR wrote: post #62

My biggest issue with .net core and .net in general, although .net core seems worse, is nuget issues and it causing issues with binding redirects. Seems like every project I waste hours trying to figure out the mess that nuget creates.

Same here. I've tried moving my "boilerplate side project" .NET Framework template over to the latest and greatest about once a year over the past four years and every time I hit the eight hour mark, I give up. Either my dependencies aren't supported yet, or there's some wonky versioning incompatibility, or there's some other undocumented frustration. I'm not dealing with anything wildly complex here ~ just an n-tier architecture supporting MVC rendered views, forms authentication, API endpoints, an EF middle-tier, and Azure SQL. About as simple as it gets for a web app.

Has anyone here migrated from .NET framework > .NET core lately? Think it's time for me to give it another go?

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#253

Post by velox_io »

cm2187 wrote: post #121
gnud wrote: post #41

Earlier quoted context omitted.

I love it every time I get the 'old' control panel. It means I know where the switches are, and more importantly, what they do. The new UIs change with every minor update. Layout, labels and semantics. It's truly horrible. Please don't encourage Microsoft to mess it up even more.

And also items from the old control panel don't appear any more when you search in the start menu. Which would be ok if they had been replaced by an equivalent in the new menu. But they have not. So what is the point in hiding them?

They're removing the pre-Windows 10 Control Panel items with a new Settings interface. The problem is that it's far worse:-

Tasks such as changing network adaptors setting, or sound settings. I regularly switch between three different audio devices on my desktop PC, and doing simple tasks such as toggling volume levelling isn't in the new interface and digging into the old is becoming harder and harder to find, with more clicks for every revision. Just yesterday I went to add a firewall rule, and that was hard to find. I'm an MCSE, so you would think I could change a firewall setting!

It definitely doesn't feel like an improvement, it feels like they're forcing an abstraction. Plus they've recently removed the Control Panel when you right-click the Start menu. That was about the only 'Safe Space' left.

I feel for anyone who has to support Windows 10. They're definitely not listening to the users. This is the FisherPrice interface all over again, but there's no stopping it this time around.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#254

Post by DennisP »

wlesieutre wrote: post #238
DennisP wrote: post #178

Earlier quoted context omitted.

I've got a Macbook Pro and it doesn't seem to have or need this feature in the first place.

It does have an analogous feature, the MBP's trackpad is huge and you probably touch it by accident all the time. It's just that Apple's system tries to separate deliberate touches from accidental ones, rather than disabling the trackpad input completely. You used to be able to turn this on and off (it was called "Ignore accidental trackpad input" in the trackpad preference pane) but now it's an always on feature. Th…

Yes, I touch the pad by accident all the time. But why is Apple so good at detecting which touches are accidental, while so many other manufacturers are not?

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#255

Post by WorldMaker »

mirekrusin wrote: post #51
mariusmg wrote: post #9

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 :)

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

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

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#256

Post by e12e »

oblio wrote: post #34
codeulike wrote: post #28

Earlier quoted context omitted.

- Allow functions outside of classes What do you mean? Isn't that just anonymous functions?

He wants top level functions. He wants to not have to write classes if he thinks the domain doesn't need modelling as objects.

They probably wants to not have to write classes if he thinks the domain doesn't need modelling as classes.

Objects are just initialized memory with a vtable, or actors that sends and receives messages...

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#257

Post by jayd16 »

goto11 wrote: post #181
rafaelvasco wrote: post #170

Earlier quoted context omitted.

Don't get why people want floating functions. It makes easier to do bad coding and architecture imo. At least you must namespace them;

Consider something like the Math class. In practice it just works like a namespace for math-related functions. The only reason to have a class is because the language requires it. It would certainly be cleaner without having to define a useless class.

Yeah, except I like that Log() isn't already a reserved function name.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#259

Post by jongalloway2 »

mjfisher wrote: post #6

Can anyone closer to the .NET community than I am comment on the wider adoption of .NET core on standard line of business applications? The few places I know that work with .NET are a long way from migrating yet. Are there any similarities with the Python 2/3 port? I imagine language level compatibility makes the transition much easier.

Here's the customer showcase on the .NET site (with links to more at the bottom of the page). It lists some of the biggest enterprise adopters: https://dotnet.microsoft.com/platform/customers

Of course, lots of Microsoft services run on .NET Core. Last year, the Bing team talked about how their move to .NET Core 2.1 gave them big performance jumps here: https://devblogs.microsoft.com/dotnet/bing-com-runs-on-net-c...

(disclaimer: Microsoft employee, .NET team)

Post reply on HN