Відео

XUnit documentation is trash, it's the worst I've ever seen.

Great video. I was confused on where to put infrastructure codes.

Thanks your insights of this book!

There are economic reasons. Excitement and challenges keep devs moving forward, helping us land better-paying jobs when a raise doesn’t come through.

All beautiful until jsou need to nest 3 methods returning result...

9:34 I've using Windows for a long time so that's so weird when I see the Macs needs an app to position the windows on screen xd

That's a great one about some tips when using Rider 👌 I've started using after they license model change, and I really like it, the debugging experience is really cool as well as the amount of refactors suggested. The IDE in general is fantastic. Nonetheless, I think that VS has close the gap a lot in terms of usability and performance, so both are two amazing options!

Thanks for sharing these insights. 🙏.

Nice one.. Is there a way to create a dynamkc consumer using Kafka flow? Say i have a multi tenant app where each tenant kafka broker details i will get at run time. And also each tenant will have there its consumer setting like batch count, timeout and other setting. Could you pour some inpiut on this?

keep going thanks so much

The title of this video is "Why We ALL". But in the video, you say, "most of us". Please don't do titles like that. Also, as of today, xUnit has 564,204,215 downloads on NuGet. NUnit has 412,892,074. That doesn't seem like that big of a difference. FWIW, my choice is always NUnit.

This is really nice explanation especially adding the notes at 5:12 which helped me giving a background why we need limit and offset.

Thanks for the bananotate love ❤️❤️

in windows Banana 🥲🥲

Added Grammarly to my list

Você conseguiu resolver no Cursor para fazer o debug de .Net? Em outro vídeo seu, disponibilizou um link em que era muito trabalhoso adequar a ferramenta. Conseguiu uma maneira mais fácil?

Só BR fazendo conteúdo brabo demais kkk

There's no app that could mac os not suck absolute ass. Worst OS hands down.

App 1 = Bananotate App 2 = Grammarly Pro App 3 = ProtonVPN App 4 = Rectangle App App 5 = Cursor AI

The key point of using test doubles and fakes in particular is the maintainability. They prevent your test cases from being coupled to the interfaces of the system. This is imho the biggest issue with using mocking libraries. You’ll realise this once you break 50 cases by modifying an interface and you know none of the intended behaviour actually broke and you realise you need to modify all those mock setups. You’ll wonder what did I do wrong, why is unit testing and TDD so highly praised, there’s so much maintenance, It’s the quickest way to put people off of unit testing and TDD.

Well, I guess the hard part about legacy code is figuring out the test cases when there's no one who could tell you. Unfortunately Verify and code coverage tools can't fix the fallacy of a hire and fire policy.

Do you provide or point to a place to put this architecture at practice for example in React/Next.js apps?.

My last comment

Interesting use, great video!

Hi, thanks for the video) and what is your terminal theme/customization?

The lib hasnt been updated in a year... do you think it is still alive really?

And I would like very much a video on integration testing with TUnit

I'm on Linux and use Rider, so the command line is absolutely fine for now :) The expectation that a new framework - for anything - gives the same experience than established solutions is a problem for all new things. The problem is on our part, we have to let go of comfort. But if the core idea has merit, and for TUnit it looks like it definitely does, that means when we get behind it, the discomfort is only tempory. And I would like to see TUnit next to my go-to xUnit and the others in Rider.

I have still some questions about this? How would you test that your ef mapping to your domain classes? And also How would you tests your db migration script? I think both of them would be more an intégration test.

I'm trying Before and After attribute, can't get it to work. I have to inherit it in my test class. As well as use the attribute. Mine is TestCommon : BeforeAndAfterTest. In my test class I inherit : TestCommon as well as use the {TestCommon] decorator / attribute for the test I want to apply it to. I'm setting up an Edge Browser in the Test Common file. It's null as soon as I leave the Before method. So the life cycle doesn't seem to be happening here. The TestCommon class, with Before method and After method in it, evidently is destroyed when I leave the Before method. When I get to the test, the instance of the browser is null. I am populating a public property of type EdgeBrowser in Test Common class. I'm seeing it in the Test. I traced this through during debug. As soon as the closing curly brace is hit, I have no more browser. So when the code in the test is hit next, the browser instance is NULL. Please show the entire file set up for the test using the [BeforeAndAfter] attribute. It would be useful to see how you're doing this. The video shows just the [BeforeAndAfter] decorator being applied. It makes one assume this is all that is needed but this can't be right. Thanks!

From the intro he looks like he just started studying programming, and he has no idea what he's talking about

Very deep rabbit hole and frustrating. Thank you for confirming us devs aren't the crazy ones. The only thing documented worse than security is .NET Maui.

keep it up Sir!

Keep going, I do love your content.

how would you handle when one feature talks to another do you call them directly or duplicate the code?

Is this infrastructure folder contains the implementation of external services communication? Like repositories, Http API integrations, Blob storage and so on? is it shared and global to all features? It seems pretty similar to Infra layer of the layered approach, right?

In my personal experience I rarely see any developer use xUnit. I see a wider adoption for MSTest and NUnit. Recently I have been researching what are the pro's and con's of using each framework. I must say that NUnit, xUnit and MSTest can practically do the same things. For some features you need to rely on additional libraries with all tests. However relying on additional libraries isn't necessarily a good thing. Still if I must make a choice of which one is better, my choice would be NUnit, because it has the most expansive and up-to-date documentation. MSTest and xUnit's documentation is actually hot garbage. One needs to rely on blogs and youtube video's of others, that try to make sense of those frameworks, and hope they are still relevant.

Can i become a professional .net programmer with mac m1 ? Thanks in advance ❤

6:42 I DO like the idea of not duplicating based on context because then I don't have to have unnecessarily long names. The fact that you have many names that are the same (like Request) in different folders makes it easy to know what it's doing and it's easier to implement a naming convention. A big selling point of vertical slice architecture is that you're mostly only working on one feature at a time so smaller class names is easief to understand. Having said that it would be better if the IDE could be set up for someone who wants to do VSA. Thanks for the video

Thanks a lot Gui, awesome as usual 👍 I have a question about Clean architecture and file upload, Is it ok if used IFormFile in Application project as a parameter in the IRequest class/record public record CreateArticleRequest(string Title, string Content, IFormFile ThumbnailImage) : IRequest<Result<CreateArticleResponse>>; or create a custom class and map IFormFile to it in the controller public record CreateArticleRequest(string Title, string Content, FileUploader ThumbnailImage) : IRequest<Result<CreateArticleResponse>>; public async Task<IActionResult> CreateArticle([FromForm]CreateArticleRequest command,[FromForm] IFormFile formFile) { command.FileUpoader = formFile.MapToFileUploader(); //... } or you have a better approach ?

video start at 3:00

Smart steps into can also be accessed by clicking the 3 dots during debug on the left bottom.

What is the font used for IDE? Project Explorer etc? I use default on the latest Rider version, and yours seems more appealing... Thanks for letting me know.

The visitor pattern works great for serializing / deserializing syntax trees. That's the typical case I know.

I really enjoyed seeing your learning and experiment journey learning this. It was very helpful to see that.