It is a really great framework.

You are welcome.

Request the AI to act as a client and provide the requirements in the selected domain 😊

That is tricky, but it is part of the process of gathering requirements. Yes, you can use AI, but also do research into the topic yourself. Look at other sites and apps that are used by the target audience. See what features they have. See what they brag about having. Working in a business environment will require you to build up these investigation skills. You will need to know subjects better than even your clients in order to most effectively create applications for them.

It all depends on your situation. Just remember that it is only showing people what is already there (and probably documented somewhere).

😂

lol

Yes, I can see that. However, this is also an opportunity for you to clean up and improve your API so that it handles abuse.

That works for most people.

You are welcome.

😂

Thanks!

Thank you!

That is a big part.

You are welcome.

Yeah, I was happy that JetBrains added the free tier. That makes it much easier for me to promote. I don't want people to think that getting into software development requires a lot of up-front expenses. People get so caught up in buying things thinking they are making progress rather than taking the time to do the actual work.

@@IAmTimCorey I think it is great, Jetbrains is not as big as the beast which is Microsoft, but they have an amazing IDE and I prefer Rider to Visual Studio. I don't think I could ever go back to Visual Studio, but I doubt I will ever go back to Windows at this point either. Looking forward to Game Dev and some Aspire content on DevPass.

That's coming.

@@IAmTimCorey@IAmTimCorey I had an app on VB6 that was to migrate up to C#, it was pretty interesting in that it contained Fortran and, at the time, did machine learning.

@@IAmTimCorey Waiting for that

I’m updating a .NET 5 app to .NET 8 and it’s a real pain. Getting there though but it drops the startup file and there are changes to db context.

WebAssembly allows you to work without a connection to the server. Server requires a constantly open connection back to your server using SignalR. If this connection gets broken, your web app is broken and will need to be refreshed. WebAssembly doesn't require this, thus it reduces your overall resources needed. Plus, the processing is all done on the client-side instead of the server-side, meaning that your server can handle more concurrent connections when you switch to WebAssembly.

@ first of all: Thank you for your helpful videos and your comment. I understand these benefits. But I think I didn’t wrote my question clear enough (sorry English is not my first language). I often read, that WebAssemblies also enhance the user experience due to that you can have user inputs and interactions with the page and that serverside Blazor are more or less static websites. But with these new RenderModes and Connection types isn’t it possible to have the same experience as with WebAssemblies? I really tried to find that out via google but couldn’t find any answer wich would help me chose between them. I am currently working on a new project and wanted to use Blazor. I won’t have many user but I will have lots of data and documents being loaded and displayed. I really would appreciate your opinion on that matter. And again thank you!

It has been a while since I worked with an AS400. It just takes a DateTime as a string format with a specific layout, right? If so, you can just do the ToString("mm/dd/yyyy") method to output it to the correct format (obviously I just used a sample format - you would create the one that the AS400 needs).

I'm glad it is going to save you time.

You are welcome.

And there is a reason for that - context is important. New developers tend to want to just know how to use something. "Learn" it in 2 minutes. The problem is that you then think you know something, but you have no clue how to actually use it correctly in production. Employers aren't looking for you to know trivia. They are looking for you to know how to actually do the job. That's what I try to impart in these videos - a better understanding of why, when, and when not to use something, not just how to use it.

@ you’re right. I got impatient. It’s a race between trying to understand quick to pass an exam and that. Thanks for the content though. Can’t be easy doing it for free and have assholes like me in your comment section

😂 I understand. There's always a balance. That's why I also have 10-minute training videos and KZbin shorts as well. Not everything can be covered in every format, but I do my best to meet people where they are at. Just keep in mind that passing the exam is great, but it doesn't equate to real-world readiness. Take the time whenever possible to get the strong foundation you need.

You are welcome.

Keep it really simple - is there any game that you've played with a friend? Maybe darts or checkers. In those games, you probably kept score. In darts, it might be the total points for and against. In checkers, it might just be how many games each of you won (or just 1-0, meaning one person one and the other person lost). In either scenario, that would be a match. Now, imagine you have three friends and you want to see who is the best at darts. So, you and friend1 play. Then, friend2 and friend3 play. Let's say you win your game and friend3 wins their game. Now, you and friend3 play a game. Whoever wins that game is the overall winner. You've just run a tournament. The tricky bit comes in when you have not enough people for everyone to match up. For example, what if it were just you and two friends? Well, in that case, you might play friend1 while friend2 waited. Then, if you won you would play friend2. Compare that to the first scenario. Friend2 basically didn't have to play the first "round". We call that a bye, meaning they automatically "win" their first "game" because they don't have anyone to play against. That's basically it. You now have the knowledge of tournaments, rounds, matches, and byes. That's all you need to know in order to build this app. That's one of the skills that is valuable to learn as a developer - learning new concepts outside of development. For instance, I worked at an insurance company for a couple of years. I had to learn how insurance worked so that I could build systems to support the insurance industry.

@ I was lost with the “bye” concept. Thanks for explaining it so well !

Script debugging is tricky, because scripts often have bugs that are just passed over. The web can be a messy place.

Is the best practice to leave it on or off?

I'd leave it off typically until you need it.

Yep, you have to go back and add it again. Sometimes that list gets wiped out.

@ super annoying. Thanks tho!

We used SQL in this video, so it will be exactly the same (if you are using the .NET Framework, like we are in this video). If you are using .NET 9 (or other versions of .NET), the code will look a bit different, but the actual Dapper code will be almost exactly the same.

I'm not sure what you are expecting here, though. If you are on an air-gapped system where security is not a problem, you don't need to upgrade. Microsoft isn't forcing you to upgrade. You can use one version of .NET for as long as you want. You won't be supported by Microsoft, but I'm not sure what you are expecting from that support. That support means that they will fix bugs in .NET and address security issues. If those two aren't an issue for you, you don't need to upgrade and you don't need support. You can run on .NET 6 practically forever. Just make sure to include .NET when you do your installations so that you always have the correct version on the client. The issues will be more a matter of the world passing you by, your code will become harder and harder to upgrade if you ever want to in the future, and employees that want to work on your systems will be harder to find. You may need to freeze the version of Windows you have at some point, as well as the version of Visual Studio you use. You will also need to be sure that any third-party libraries you use are downloaded and served locally, since some will go away and others will remove support for older versions of their packages. In the world of software development, an LTS of 20 years is not possible. Think about it. 20 years ago, Windows XP was just out. Computers had Pentium 4s (32 bit processors were common) with 256MB of RAM. Spinning 5400RPM hard drives were common. You want software written in this era to still be supported today? How much are you willing to pay for that? From Microsoft's perspective, with a minimal team, you are talking about millions of dollars per year. Now, let's say Microsoft goes for it and you are using it. Now, 20 years later, support is up. What then? Are you going to upgrade to .NET 9? From .NET Framework 1? The incredible thing is, from Microsoft's perspective, you can actually do that, but I highly doubt you can physically do it. That means that your app is going to be out of support. The outcome didn't change. The only real difference is that it is more likely for the app to stay out of support this way.

@@IAmTimCorey I don't disagree with you in any way. What I am saying is that there are lots of places where upgrading every 2-3 years is too fast. I worked in an airport before, some of their systems were really old, but perfectly adequate. Yes, when you upgrade it is likely it will be to a new OS version and a lot of dotnet versions newer. Yes, many developers like to be on the latest and greatest, but there are very good money to be made with ancient languages (ex: fighter avionics, F16 is older than me and still very popular) and I see nothing wrong there. And yes, we pay Microsoft a lot more than millions for support of old stuff and it is cheaper that way. So, you are perfectly right, just don't forget about the significant portion of use cases where LTS is too short. Why do I say that? Because when we need consulting, people like you are on the list to ask for it. But if you are not aware of this kind of clients and their general perspective, you might not be able to understand them well enough to help them.

OK, so I get what you are saying. You aren't really advocating for a longer LTS as much as a longer extended support contract window. Yep, I can see that. The issue is it really is a custom thing. It should almost be treated as a separate language at that point. There is so much that goes into super-long support windows like this. They are necessary, but difficult to get right.

You are welcome.

I'm going to do a video on support windows and why longer LTS windows are actually a bad thing.

Knowing WPF well definitely closes the gap a lot in terms of speed, although I would argue that drag and drop design is always going to be quicker at the start. Once you get into complexity or detail, XAML will be faster, but there is still a tipping point.