Earlier quoted context omitted.
The whole runtime gets included in the binary.
How much does this add to the binary's size?
Something like 60MB if the application is not trimmed. Closer to 10MB if the application can be trimmed.
.NET 6 Released
331–340 of 428 posts
Re: .NET 6 Released
#332Earlier quoted context omitted.
I can chime in on this one. I think it's very much a 'culture' thing. So, I'm a *nix guy. You know, running Sway WM, using Doom Emacs as my daily driver, that sort of a thing. Learned vim to write my thesis at night on an armchair where using the mouse was not comfortable. Not long ago I accidentally got involved with a kind of a .NET consulting gig. Rather, I got involved as a domain expert to help out some SaaS sta…
> But I won't be looking for .NET jobs Have heard this sentiment in more than one comment in places like HN. "The {tech} is great, but the culture was ... so I'm not putting {tech} on my resume". And So it becomes a self-fulfilling prophecy :). Yet some tech seem immune to this. They don't say "X is great but the culture was crap, so I'm abandoning X", they say "X is great but the culture was crap so I'm changing job…
I see your point.
But then, do you really believe one would be a smart person if they were to look for .NET jobs where at the same time Windows is not the dominant environment that people use at work?
Re: .NET 6 Released
#333Earlier quoted context omitted.
I've been waiting for .NET 6 for the past year for the long term support. As much as I wanted to use .NET 5, I figured it would be best to only use LTS releases in production.
I never run anything else than LTS in production. The in-between versions have basically been beta quality since .NET 1-preview.
Disagree. .NET 5 and 6 previews have been remarkably solid+stable for me.
Re: .NET 6 Released
#334Earlier quoted context omitted.
They just keep recognizing that WinForms is the best. And you can still use it
Do they have full support in .net 6? I believe in previous version it was a partial/beta implementation. Hardly any mention of winform in the announcement. I am basically stuck on .net 4.8 because of that.
WinForms support in .NET 5 and 6 is great. It's getting a lot more attention than WPF (which is owned by the Windows team), and it's likely that in .NET 7 it will be trimmable and maybe even AOT-compatible.
Re: .NET 6 Released
#335Earlier quoted context omitted.
> and LINQ Shudders at memories of coworkers writing giant, ridiculously inefficient LINQ queries without understanding how it's actually using the database and what it's doing server-side > Toplevel programs should make it easier to experiment with C# if you're interested. Definitely interested in that small feature :) If I had extra time I'd like to see what it takes to brew install dotnet and write a simple CLI pr…
> Can .NET deploy a static binary nowadays? You can bundle everything in a single file but that file contains the runtime, so even small Hello World apps are 50MB+ last I checked, though there have been some improvements recently with trimming and AOT is hopefully coming next year with .NET 7.
Yeah, starts closer to 12MB for a trimmed console app in .NET 6. It works really well (I've been distributing one for a few months now).
Re: .NET 6 Released
#336For me Hot Reload is the most important feature, which will very likely be a reason for me to move a bit from Python over to .NET, which I haven't touched for 10 years. Back then I really used it a lot (after moving away from OLE/DCOM/ActiveX), in C++, Managed C++, C# and IronPython (no GIL!). I absolutely loved it, but it was limited to the Microsoft ecosystem. Yesterday, while randomly googling for "hot reload" I g…
I think the Hot Reload stuff is still in its infancy.
From what I read, it doesn't yet support stuff like async/await, LINQ, lambdas (and few other things). And those are used a lot in modern .NET apps.
Still a great improvement in the right direction.
Re: .NET 6 Released
#337> In .NET 6, in-memory single file apps have been enabled for Windows and macOS. In .NET 5, this deployment type was limited to Linux. You can now publish a single-file binary that is both deployed and launched as a single file, for all supported OSes. Single files apps no longer extract any core runtime assemblies to temporary directories. This is a great! Now I can publish statically linked executables and run it e…
I wish that I knew about this earlier. I'm a Linux user but I love C#. I suppose that VS Code is the canonical IDE for C# today?
Re: .NET 6 Released
#338Earlier quoted context omitted.
Also if you still need to support XP (even back when it was still getting patches), forget it, Microsoft has no interest in supporting you. Even if you want to use the latest and greatest UI, your customers need to keep up too. Completely unworkable.
XP is 20 years old, its older than invasion of Afganistan.
I recently ran XP in a VM inside Windows 10 and was amazed at how much faster everything ran, how quickly programs start, and how responsive they are. Feels like we lost something along the way...
Re: .NET 6 Released
#339>> ASP.NET Core in .NET 6. I've been on .net since 1.1 and .net Core since 1.0 and this statement makes me so confused. Core lives _inside_ of .net 6? Is there a non-core ASP.NET that also lives inside that framework? I thought .net 5 was where the legacy 4.x branch and core 3.1 was married in holy matrimony, minus the worst of the legacy garbage.
.NET is sane now... .NET 5, .NET 6, .NET 7... all cool, no more confusion going forward... .NET Framework(full Windows only Framework) is .NET Framework 4.x, stuck there forever only security patches... Only remaining confusing part left in ecosystem is "ASP.NET Core", because even though .NET got rid of Core, latest version ASP.NET didn't
It’s easy. You have .NET Framework 4.8 which is followed by netcore 3.1 which is followed by .NET 5 and now 6. 4.8 supports netstandard 2, core and 5 additionally support netstandard 2.1. You can then use ASP.NET with 4.8 or ASP.NET Core with 3.1 onward. Entity Framework is only supported on 4.8 and Entity Framework Core up to 3.1 support netstandard 2 so .NET 4.8 and 3.1 onwards both. But the versions after 3.1 (obviously they went to 5 there) only support netstandard 2.1 so only dot net core 3.1 and onwards.
Perfectly clear and reasonable.
Re: .NET 6 Released
#340Is there a mature(!) webview library for .NET so I can build cross-platform GUIs with HTML/JS/React but write the backend in C#/F# and bundle that whole thing into a single file (not a zip/something that gets extracted on run) for every platform?
You may want to take a look at Chromely and its WebView2 offshoot EdgeSharp:
https://github.com/chromelyapps/Chromely https://github.com/webview2/EdgeSharp