Where do we use 'dynamic loading assembly' in .net app.
We can dynamically load an assembly to project without needed to add the reference to that assembly.. but its a developer intiative to add the references t o the project, one time task...once executed it binds to the projects. Then in what senerio we use this dynamic loading assemblies comes in. can anyone cleare my doubt..
Re: Where do we use 'dynamic loading assembly' in .net app.
The most common scenario that I'm aware of is to create a plug-in architecture for your app. You define an interface that all plug-ins must implement, then developers will build libraries that implement it. At run time your app will browse its plug-in folder and load any assemblies it finds. It will use reflection to determine whether they implement your plug-in interface and, if they do, it will consider them as part of the application.