ASP.NET Core VS .NET Runtime

I believe you can start create a 'whole' frontend + backend with asp.net core + blazor.

I mean you could use blazor to create 'front end' and use asp.net to create server side

This might be a dumb question but I can't seem to get my head around it. I am starting a process from a ASP.NET Core controller and it works fine. I can also close the application from the same controller with no issues. What is the benefit of WaitForExit()? Do I not need WaitForExit() if I am closing the process programmatically when the controller endpoint is hit? (yes I am aware I would use WaitForExitAsync() since its asp dot net )

The problem here is, no single person should be owning this decision. If asp.net core fails and bob suggested, it isn't his fault. Your team collectively should agree on some core principles you are looking for in your tech stack. Figure out where you rank the importance of scalability, cost, existing documentation/support, performance, and team knowledge. Then someone (or everyone) can do some research on where each stack is in those areas, with some supporting articles etc. Then have another meeting to go through what you found, and get consensus or even vote based on the outcome.

i never took courses because i did not get any value from it the only thing i recomend is building simple apps like console apps and after that start progressing to winform and then asp.net

the first language that I taught myself is c#, I remember building a WinForms app that read images from the scanner and display it in a PictureBox, it was hard especially with no programming basics, but I was so happy when I saw it running. a couple of years later I found myself knowing c# java c++ swift PHP asp.net .netcore android xamarin and some sort of reverse engineering, I found my first job by finding a vulnerability in saml2.0 protocol when the public key is not validated by the authority signer which means you can modify the assertion sign it and gain access control over sensitive accounts, the only problem I faced was the response time was validated and I have only couple seconds to modify the data sign it and send it. long story short I had to capture the data through fiddler core insert my cert get the response URL, decode it, modify the XML, sign it and send it back.

API in asp.net core with sql database for the basic features like signup,login,retrive rank cards..etc

- C# (ASP.NET and Blazor)

You can also secure an entire blazor server side app using asp.net authentication and authorization services. My app is protected using open ID connect and it only takes a little config in the startup config and one attribute on the _Host.cshtml (@attribute [Authorize])

- Codewrinkles he has playlist: Asp.net core for absolute begginers ( I suggest start from this) -Tedy Smith asp.net core webapi he start tutorial one week ago

StopTheHostException should be made public to be dealt with gracefully #60600 - GitHub

I ended up filing an issue on GitHub. They then filed a new issue which is still open today.

How .NET Framework (or latest .NET) implemented a certain function / feature, how it varies different design / implementation decisions in reality, etc. (remember 1. the latest .NET is open-source under MIT license. 2. .NET Framework 4.8 Reference Source is not; it is under a thing called MS-RSL. But still you can look at it)

Most of the article basically describes a workaround that Microsoft themselves needed to implement because .NET Core and .NET Framework don’t support in-process side-by-side hosting: https://github.com/dotnet/runtime/issues/53729

runtime/src/libraries/System.Security.Cryptography.Cng/src/System/Security/Cryptography at main · dotnet/runtime (github.com)

There are much better APIs now on types such as Aes, HMAC and IncrementalHash, with support for one-shot operations and Span interop. Your best friends are the API docs, .NET API browser, and just looking at issues and PRs in the runtime repo such as this, this or this 🙂

which could be due to NTLM incompatibility: https://github.com/dotnet/runtime/issues/887

https://github.com/dotnet/runtime/issues/49397 and https://github.com/dotnet/runtime/issues/63331 go into more detail about the APIs that are being added, with just Shuffle left to implement.