Live data from Hacker News

.NET 5.0

devblogs.microsoft.com

461–466 of 466 posts

Re: .NET 5.0

#461
I really like where thing are heading with .NET.

On the other hand, I'm still missing an easier interop with other ecosystems. C# is an easy to use language and I would love to write some common code / business logic / whatever you name it in C# and expose it as webassembly and C/C++, this would cover mobile, web and desktop workloads. You can do something like that with Rust (or at least they claim it, I never tried), but with C# I don't see any _easy way_ doing it. I would be happy if someone could correct me If I'm wrong.

Re: .NET 5.0

#462
post #460

Earlier quoted context omitted.

Honestly our stuff is pretty pedestrian. We have a front end website and API service, a couple of application servers for our telemetry IoT outstations and of course a backend database server.

I think you'll be fine with Azure then. You should use the pricing calculator beforehand to not be surprised by the costs and figure out how to reduce them but this applies to any cloud provider.

Thanks for the reply MaKey. Thats good advice.

Re: .NET 5.0

#463

Earlier quoted context omitted.

This is technically true, but it's a difference of a 5 MB executable vs a 50 MB.

.NET has trimming now, so it is 5 MB? (Possibly less!)

Nope.

Running this command:

    dotnet publish `
    -p:Configuration=Release `
    -p:PublishSingleFile=true `
    -p:PublishTrimmed=true `
    -p:RuntimeIdentifier=win-x64
gives an 11 MB file, that still requires 4 DLL as well.

Re: .NET 5.0

#464
post #129

Earlier quoted context omitted.

you can use property injection when you use something like autofac as the di container.

Cool, so I'll add another dependency and figure out how to use that, to save myself time having to write out MS's convoluted dependency-injected configuration code.

Meanwhile one could of have this solved in their projects in less than the time it took to have this HN discussion and moved on with their life. Seriously, somethings are worth complaining over, others are not.

Re: .NET 5.0

#465
post #459
post #392

Earlier quoted context omitted.

Yeah, I'm pretty shocked how much hate it seems to get. Maybe it just makes things easier for simpletons like me? The one issue I can see with DI in ASP.NET Core is that it doesn't really do DI correctly. The point of DI is that ultimately, you have complete control over how you build your dependency graph and you shouldn't be forced to use a container at all if you don't want to. With a DI abstraction the developers…

That is 4 years old, is it still relevant?

Yeah, that whole approach hasn't really changed at all. I'm not sure how MS could even realistically change it without breaking a lot of stuff, so I think it's more of an example of what to avoid.

Re: .NET 5.0

#466

Earlier quoted context omitted.

Thanks, I will make sure to check this out. Does anyone have any articles or documentation on this?

Stacktrace improvements in .NET Core 2.1: Intelligible stack traces for async, iterators and Dictionary (key not found) https://www.ageofascent.com/2018/01/26/stack-trace-for-excep...

Awesome! Thank you. Wonderful to see these open source contributions to .NET.
Post reply on HN