You are welcome, Aditya

Thanks for the feedback! I'll keep it in mind for future videos.

Yes, generative AI has limitations like dependency on training data, lack of deep contextual understanding, and high computational demands. It can produce plausible but inaccurate results, faces ethical concerns, and may struggle with reasoning or scalability. Developers must validate outputs and mitigate risks carefully

You are welcome

Glad you found the demo helpful! 😊 I’d recommend starting with Microsoft Learn - it’s a solid foundation and gives you hands-on practice with the basics. Once you're comfortable, diving into more advanced topics will feel much easier. Good luck, and feel free to reach out if you have questions along the way!

What are the new trendy questions ?

Thanks for the feedback, Amit.

Great question! Yes, using a parameterized query in a stored procedure is definitely an option and is often preferred for better security and performance. It helps prevent SQL injection attacks and optimizes execution. Thanks for bringing it up!

Good question! When moving to production, it’s best to follow the principle of least privilege. Assign access policies in Azure Key Vault that only give the necessary permissions (e.g., Get, List) to production apps or managed identities. You can also use Azure RBAC for more granular control. This ensures secure and controlled access without over-privileging. Let me know if you need more details!

Both are great resources, and it depends on what you're looking for! *C# 10 and .NET 6 by Andrew Troelsen and Phil Japikse* is excellent for a structured, in-depth approach, especially if you prefer a book that dives into .NET and C# together with hands-on examples. *C# in a Nutshell* is fantastic as a comprehensive reference, covering the language features and ecosystem concisely-perfect if you’re looking for something you can refer to often. If you're just starting, Troelsen’s book might feel more beginner-friendly, but for quick lookups and advanced insights, *C# in a Nutshell* is solid. Hope that helps!

Thanks for the appreciation

Great question! Both approaches could work, but each has its strengths. Adding partner users as guest B2B users in MS Entra ID is often a simpler route if you mainly need to grant access to users from a few partner organizations. It allows you to leverage your existing MS Entra ID setup without significant changes to the application and offers a streamlined way to manage access using your current policies. However, if your application expects to onboard users from many different partners, or if those partners use various identity providers (not just Microsoft), Azure B2C might be the better choice. With B2C, you can set up federations for your MS Entra ID and any other identity systems partners use, providing a more scalable and flexible authentication model. It really depends on how many partner organizations you anticipate and how diverse their IAM systems are. Let me know if you need more details on either option!

Hi Supriya The example of a bill versus an invoice aims to illustrate the nuanced complexities that arise when we attempt to share a domain or vocabulary across different applications, departments, organizations, and geographical boundaries. The essence of the 'bounded context' concept, a strategic pattern in domain-driven design, is about recognizing and respecting these nuances. It emphasizes the importance of establishing clear boundaries within which a common domain model or vocabulary is applicable and outside of which it may not be relevant or understood in the same way. When we say that a bill in one country might be considered an invoice in another, it's not suggesting a necessity to split systems merely due to geographical differences. Rather, it's highlighting how the meaning and usage of terms can vary significantly across different contexts - be they cultural, organizational, or functional. The key takeaway is that what's considered common or standard in one bounded context might not translate directly to another, despite apparent similarities. Bounded contexts enable us to delineate where a particular model, language, or set of assumptions is valid. This delineation helps in managing complexity by allowing systems or departments to interact through well-defined interfaces and translations, rather than assuming a universal understanding or application of concepts across all areas. This approach not only caters to variations in terminology but also addresses differences in processes, regulatory requirements, and cultural norms. In essence, the bounded context is about acknowledging and planning for diversity in interpretations and requirements. It guides us in designing systems that are more adaptable and easier to integrate by recognizing the boundaries within which our models and terminologies make sense and where they might need translation or adaptation. Thank you, Vikas

check out this Video by Suresh where explains Domain Driven Design including Bounded Context kzbin.infovZ3OnaqPR7c

We are going to another live on DDD on Apr 6. Stay connected

Thanks for the feedback

Well summarized.

Thanks for Positive feedback

Thanks for the positive feedback

Thanks for feedback. I will check the video for clarity

you sound like a friendly and compassionate person

Hi Omar, Thanks for comments. Sorry to hear about you job loss. I have recently switched the job . Message me on Linked in , I may be able to give you tips. Best of luck, Vikas Kerni

Thank you, Aditya

Thanks for sharing your thoughts! Stored procedures and views definitely offer powerful ways to handle complex queries, especially for performance tuning and reusability. ORMs, on the other hand, can simplify code management and reduce boilerplate for many applications, especially when working with smaller or more dynamic queries. Ultimately, I think it comes down to project needs and team preferences. Both have their strengths-appreciate the input!

You are welcome

You are welcome.

Agree

You are welcome , Nihal

Correct. Lot of us started with MVP and switched to MVC later because of Classic ASP and Web Forms restrictions. I thought that it will be easier to explain two patterns if I started explaining MVP, its limitation and move to MVC patterns. Vikas

Thanks Ayush for being core member of the group. I appreciate your hard work and discipline. Wish you great success in your career. Vikas