We Need TWO?! - C# Plugin Architecture For Core

In the previous videos I made on this topic, we looked at two different ways that we can setup Autofac for dependency injection inside of Core. There were pros and cons to both approaches, but for the most part, they’ll do the trick for the average application. When it comes to building C# plugin architectures, I want to ensure that I have access to all of the dependencies that I’m interested in. That means in Core, I need to set the bar high for my plugins. See how I was able to combine both of the previous methods into this one! ---- Read the full article here: ---- 🔑 Membership & Subscriptions: - 📨 Weekly Newsletter: - 🏘️ Private Discord Community: - 📽️ YouTube Membership: @devleader/join 🧠 Courses: - All Courses: - Getting Started with C#: - Deep dive C#: - C# Zero to Hero BUNDLE: - Refactoring For C# Devs: - [FREE] Intro to Software Development: 🗣️ Social Media & Links: - All My Links: - Blog: - TikTok: @devleader - LinkedIn: - Threads: @ - Twitter: - Facebook: - Instagram: - GitHub: - Twitch: - YouTube: @DevLeader?sub_confirmation=1 ❤️ Affiliations & Products/Services That I Love: - VPS hosting from RackNerd: - VPS hosting from Contabo: - My newsletter platform ConverKit: - My newsletter referral system SparkLoop: - My AI shorts helper Opus Clip: - I try to help answer questions at Quora: - My favorite computer parts store Newegg: - My favorite supplement store Bulk Supplements: ---- #autofac #aspnetcore #dotnet #csharp