Introduction to Plugin Architecture in C# 

I am always amazed at the focus, and speed in which you are able to live code and explain, but what really is impressive is the amount of knowledge you have on aspnet at such a young age ;-)

Wow I learned a lot of technical things in this one video that I had never heard of or even thought about looking up in Docs. Thank you.

As usual, your content blows me off Thanks !

All of your videos are very cool, thank you!

love your stuff mate, really enjoying

Thank, that what i was looking for à long time!

Thank you, great video!

Another way to go for plug-in based architecture is source-code-based-plugins where you load the source code of a plugin at run-time, compile it, and, the rest is very similar. If the source code changes, you re-compile the code for changes to take effect.

As always a beautiful video 👍 Anyway, if you want to define middleware you can just use the IMiddleware interface

thanks, just writing a similar application and wondered why in the microsoft documentation they offer to inherit from the AssemblyLoadContext class for the sake of uncomplicated lines of code that is already in it and without me

What a great video I like the approach I think you should look for the plugin interface and what classes are implementing it in the assembly instead of the concrete class as you shouldn't know what is in the plugin yet I beleive most of the payment gateways plugins using similar approach

Great content, thank you

This is good subject. I tried similar thing using ApplicationParts and Features. In you solution, how would you pass arguments from the DI container into your plugin? do you think it possible to initialize a custom DI container in the plugin from the main DI of the application?

I really like the microkernel architecture.

Good video!

Thank you

Great content. Can you load a plugin with dependencies that are of a different version than the main app?

Superb

thank you :)

Yes. Yessss!!!

Very nice topic, sir! Wut is 'dotwatch' that you use in the terminal?

Thanks, great video like always, I was doing very similar this weekend and stumbled on the same error of not being able to unload my dll after serializing, both with newtonsoft and the microsoft one. I tried various third party and they all appear to hold a reference. Has anyone found one that doesn't stop us from unloading the plugin assembly?

Really good video, you clearly know your stuff. However, I don’t really understand what “leaking into global space” means. I was confused at the end with the serializer example and the WeakReference… why would you have to call GC 10 times…?

it was really interesting, but in nopcommerce we only write plugins and install them without chnaging anything in main nopcpmments. So is it possible for u to help us understand this

I'm sorry, I thought because of the title that this will be about c# plugins and not asp core plugins 😢 Great video though!

Cool video! What about plugin debugging?

An interesting video but I think trying to reload the plugin assemblies in-process is too fraught with pitfalls some of which this video highlights. Perhaps it would be better to just load the plugins at startup, registering the endpoints in the usual manner without custom middleware, and then have a separate process watch the plugin folder and spool up new instances of the web app, and use a reverse proxy to switch over, like you demonstrate in the 0 downtime deployment using YARP video.

Why use HttpContext instead of IContextAccessor?

This is too much voodoo

Excelent Video Thank you, but i didint get from where took pathinfo their properties values for Method and path var pathInfo = endpointType?.GetCustomAttribute(); pathInfo.Method ¿From where took its value? pathInfo .path ¿from where took its value?