Thank you very much. @dosehieu Please, I hope you post another video in the same way as part 1 & part 2, but i want it to include the following: 1. database with at least 3 tables that have one-to-many relationships. 2. use dapper instead of EF. 3. in the blazor wep app create three pages that shows every table with CRUD operation thanks in advance
Muchas gracias por el video, desde hace tiempo que quería saber cómo hacer una aplicación fullstack, solo he estudiado el desarrollo de API, no he tocado front para nada, tu video me sirvio mucho, gracias. saludos desde Colombia.
In my opinion, this is a very useful course. For those new to BlazorApp (like me). I have one question: in your opinion for "medium volume applications" which "application architecture" is better: "Clean Architecture" or "Modular Monolith"?
Thank you for your kind words! As for your question, both Microservice Architecture and Modular Monolith have their advantages, and the choice depends on your specific needs. For a medium-volume application, Modular Monolith might be more practical if you're aiming for simplicity and faster development. However, if you anticipate needing to scale or add complexity in the future, Microservice Architecture might be a better long-term choice ☺☺
@@dosehieu Thanks for the reply. One additional question. In this project, are you thinking of developing some "architecture"? Or it will be just one "monolithic application", which for "one example" is actually quite enough.
Hi @@ToniTodorov-g8z, In this project, I’m leaning towards a Modular Monolith approach for simplicity, as an example 😊 If you want to learn more about the Architecture, check out my video on Microservice Architecture here. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-CbDgOlqBvrs.html
@@garamburito Hi. Thank you for watching. Do you mean .NET Aspire? That is a lightweight framework designed to help developers get started with .NET Core in a more streamlined way, focusing on rapid development and deployment. It offers a simplified setup, essential tools, and features that are especially useful for building modern web applications with minimal overhead
Repository is implemented in ef core dbcontext class so creating the repository classes is anti pattern and caused complexity and decreasing performance.
@@MohammadKomaei Hi. EF Core does not implement the repository pattern out of the box. EF Core provides a DbContext for data access, but it doesn’t include a repository layer. The repository pattern can be implemented on top of EF Core if desired, but it is not a built-in feature.😊😊
Hi @osamaayesh9495, you can use either the Code First approach or the DB First approach. However, in real projects, we often avoid using them because we want to apply our own naming conventions. For example, if you have a new table named Order, just go to the database and create the Order table. Then, create a model class named OrderModel.cs and declare the DbSet for it in the DbContext. When you run the app, it will automatically connect them😊😊
@@dosehieu okey thanks but so if i follow ur step in this video with avoiding code first and data base i will automatically connect to sql server ? cuz u in this video didn't create database and table product so i must creat them then follow ur steps ?
Hi @osamaayesh9495, you don't need to create the database beforehand. As you can see in the DbContext, I have this Database.EnsureCreated();. The first time you run the app, if the database doesn't exist, Entity Framework will automatically create it. 😊
Hi @@osamaayesh9495 If you need to change anything, let's update both the database and the model. It will automatically connect. For example, if I want to add a column 'Discount' to the 'Product' table, just go to the database and create that column, then go to the Product model and add the 'Discount' property ☺
Hi @QaisarArsalan, I didn't use Code First in this example. If you need to make any changes to the database, first update your table, then update the model class for that table. They just need to map to each other. Migration is not required ☺☺
Hi @tavara7279, I haven't implemented authentication in this part. If you want to see authentication and role-based authorization, please check my Part 3 video here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-oqpNQxEfz_Y.html
Hi @lukevincent4397, sorry about the inconvenience. This is my first video. In the next video, I will change the font size and improve the image quality. Thank you for letting me know 😊😊
getting the following error in this code line: Database.EnsureCreated(); in appdbcontext file. Microsoft.Data.SqlClient.SqlException: 'A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)' inner exception: Win32Exception: The certificate chain was issued by an authority that is not trusted.
