1 --
In A. NET application, assume that a DLL is intended for multiple applications. ProgramSharing, the conventional solution is registered to GAC, but this solution is very troublesome and needs to be registered, it is easy to generate garbage.
(For example, in ASP. NET, it is inconvenient to update the DLL registered to GAC, especially when a large website uses Server Load balancer. CodeSynchronization ).
Problem:
Can multiple applications share the DLL without registering GAC? For example, some projects can place the DLL in the common of the Program Files folder.
2 --
Same Question 1: in ASP. NET applications, multiple web sites use many identical DLL modules. Can these sites be obtained from the same folder? (Do not use the GAC solution ).
3 --
In. NET applications, a class has a virtual or abstract method or attribute, and its benefits are obvious.
Problem:
How to make the derived subclass not reload methods or attributes that can be reloaded.