.NET Runtime VS ASP.NET Core

I really like what the .NET team has done with the Book of the Runtime, whereby they document a whole bunch of stuff about the code in the repo, but not directly in the code.

What I understand from looking at the code is that it uses the Current Culture which has rippling effects when we change that. If you could create a new discussion on the runtime repository, I'd love to get the answers from the devs.

Some wrapper methods around Windows API are not orthogonal and introduce unexpected behavior (i.e. the behavior you don't get by directly using underlying API or the OS feature). For example, look no further than Environment.SetEnvironmentVariable which will corrupt PATH variable by incorrectly expanding say %ProgramFiles%\Oracle\VirtualBox into C:\Program Files (x86)\Oracle\VirtualBox on a 64-bit OS.

It's common C# convention to use BSD/Allman-style (the OP's first one) because Microsoft has used that convention for decades and recommends it (the C# coding conventions direct to the coding guidelines for the runtime on Github).

Do be warned that .Net 6 did cause some regressions, in reflection at least

https://github.com/dotnet/runtime/issues/61486

> - Use LINQ cautiously as its variants are mostly slower than explicit coding. E.g. .Any() vs .Count == 0

Is this really true for the example? To me it seems that the implementation for .Any actually uses .Count when available, see https://github.com/dotnet/runtime/blob/main/src/libraries/Sy...

If using Net6, TryGetNonEnumeratedCount is a good way to at least attempt grabbing the count without forcing a total enumeration. https://github.com/dotnet/runtime/issues/27183

Also if you want to read more about the low level details, check out https://github.com/dotnet/runtime/blob/57bfe474518ab5b7cfe6bf7424a79ce3af9d6657/docs/design/features/DynamicPgo.md

What has gotten me quite more depressed, it is the lack of easy access to apply to my main type of jobs, which have been C# development (app, asp.net) or working stuff like nodeJS. The challening part is the lack of a phone, and everything is through that, two: Can't easily look presentable for anything, nearly no clothes, lack of cleaning supplies and cant afford public transport. Has got me to lose a lot of hope I will never be able to get back or my computer back (it is not lost, but saved so far away in a place I can't live) so basically I'm starting all the way from zero, but without the ability to properly work anything is not what I dedicated my life to last decade.

I can recommend .net. Needs some getting used to as every framework but has yet to disappoint me (including asp.net to my own surprise. It was said to be very crappy a few years back but is pretty awesome right now, at least with the limited stuff I have done so far)

asp.net core is an amazing platform to build web apps, web apis and micro-services. you can build these locally, pack them into the docker images and deploy them with ease, say, in Kubernetes, on Heroku or any cheap Linux VM with docker enabled. This is one of many reasons to use Docker for .net projects.

I am following some tutorial on ASP.NET Core.

Uglavnom taj asp.net se i najvise koristi od svih ostalih frameworka iz .NET-a, a i sada je #1 najomiljeniji backend framework po stackoverflow-u.

Hello guys, I am new at this kind of developing (front end for cross platform). Until now I have worked with c# (asp.net mvc) and databases and javascript/jquery as front end. I am getting into typescript and I like it very much. So now I have interest on front end frameworks that support typescript. I was looking at angular and I really like it, but the thing that holds me back is the release. they release so often new version with a lot of breaking changes. Ionic being a cross platform framework based on angular has the same issue. And I really like the structure of angular because of the mvc pattern. I looked on angular alternatives and stumbled on aurelia js. So far I have seen only some videos on youtube about it and it's getting my interest.

web dev is usually angular/react for companies, c# for apis, database if code-first. linq, entity framework, mvc pattern I think are good dip into asp.net ecosystem

It looks OK i guess, but why would you use this? If you're hiring asp.net developers, you would want to use a standard api controller syntax, not force them to figure out some obscure format.

The back end is ASP.net Core.