.NET, C# and ASP.NET Core tutorials, code examples, courses, videos and coding challenges for software developers to learn.
Focusing on tutorials from frameworks such as Web API, MVC and Blazor, as well as topics ranging from authorisation, dependency injection and configuration to name a few.
We'll also demonstrate some of the new features that are available when a new version of .NET and C# is released.
As a bonus, a number of our tutorials will have code examples so you can download the code from the tutorial and try it out for yourself.
Question: when we use [fromquery] but i need to recive more than one parameters, do a have to create a class? or in a method i can declare [fromquery] many time?
I would like to echo the following comment: "I cannot explain enough how this video is infinitely better than all of the Microsoft documentation combined." It's a year later, and this is still true. Thank you for the work on this video.
Nope. Maybe it is helpful in better templating, or helping juniors in setting up schoolbook application skeletons but it is beyond clueless in finding bugs, optimizing logic or generating custom algorithms. We already have non-LLM generative tools since decades, which are precise and helpful, but you only use them for specific application layers like entities or persistence. 101 in optimizing & debugging : comprehend your code. 101 in having more capabilities: clients want more and richer features
Thanks David, fantastic video. One of our front-end developers who uses Linux and Vscode is looking into moving into some backend stuff - do you have any hint for using custom nuget feeds (authenticating from Azure artifacts) and using Default Azure credentials on Linux for Azure Key Vault? Thanks
@@RoundTheCode Maybe for small-scale projects. But for an Azure DevOps implementation housing 50+ large scale enterprise repos, I think standard release pipelines are the way to go. Did microsoft come out with any docs/statements recommending to use only pipelines, not releases anymore?
I gave C# on VS Code a real try at a big work project, 8 months using this tool stack, it's extremely far from ready for any usage. The LSP is slow, eats up a lot of resources (both RAM and CPU), full of bugs, and needs to be restarted from time to time because it decides to stop working randomly, therefore, taking full minutes to reload the projects again.
I'm sorry I ever considered this ecosystem to find a job. As for you mr Round the code thaNks for the amazing video!! The tool failed me, not your content.
It's a bare-bones text editor. It's efficient in its core, use a set of movement called “VIM motions” that are (very often) useful for manipulating text (and code). Uses a language to manipulate itself (instead of JSON), so you can change and modify the editor to suit your needs.
Thankyou for this. I had a very bad time with using C# from the command line/VS Code when I had to use C# for a similar web service thing. The Visual Studio IDE has infected the C# / dotnet languages with a method of working that is very UI based. I am simultaneously impressed and disgusted that a CLI would be used to create a class. I would never have thought to try that. Obviously productivity benefits... but oh man too bad if you dont like Microsofts way of doing things i guess.
The same thing stood out to me. It never would've occurred to me to use a cli tool to create a class. I guess Microsoft wants to beat sun microsystems at creating the most convoluted boiler plate machined ever to boilerplate 😂
You can use the application to create a class etc. using Solution Explorer in VS Code if that's your preferred choice. Here's a video with more detail on it: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-r4WrDfuDT24.html
how can we find device details, like parsing from user agent .. i want to implement the new device-found functionality like google offers and send MFA on the app...
offset=2:50 as shown the category input parameter should be of type Category (i.e. that SHOULD not be null) public string? GetCategoryName(Category category) alternatively you could explicitly specify method declaration to accept nullable params with one of public string? GetCategoryName(Category? category) public string? GetCategoryName([AllowNull] Category category) so compiler would alert dodgy statements e.g. category.Name would be squiggled to warn dev to reconsider, e.g. Severity Code Description .. Warning CS8602 Dereference of a possibly null reference. Certainly your code _could_ have an early guard statement as safety-check (despite declaring "Category" as non NULLable), but I find that inconsistency to be a code-smell and I prefer using proper NRT semantics. Current project templates now include <Nullable>enable</Nullable> in generated .csproj to discourage NULL accidents.
Because in DTO you can return what you want to return to the FE team: For example, User has 2 properties, username and password, when finished, should we return the password property? I think not.
