Vb6 to VB.Net- How to replace registered dll concept -
I am replacing a VB6 application with a rewrite equivalent in VB.Net.
VB6Ap has a 'control' application that offers a form to the user and allows them to select a 'customer' from the drop down list. The reason for reading a INI file that selects the client is to set the client-specific parameter that contains many DLL's program names, which were also written in VB6 and the subjects were registered on the machine. For example, each 'client' had a different letter format, and this letter was written by the selected DLL. It forced for a while, but only one user is most likely to make it convenient for updating only that DLL and continuously updating different characters except the DLL on the old one. Thus the user (clerical) had to be asked to save this file only in the normal folder. I could compile everything in an XE together, make my updates bigger and more complex.
How do I change this kind of approach to doing it again in VBnet?
-
I can tie everything together in a big project (and compiling it in an XE which is avoiding big updates). should I?
-
If I continue with the perspective of compiling my client-specific (.net) dlls separately, is it in net Native? How do I call them? Do they need to be registered because they were first? Pros, Cons?
-
What is the right way to do this and give me still flexibility?
I will create a text-based format for you Is for. This way you have to change a template every time. But if you really want to load DLS dynamically, you can do this by using System.Addin namespace or reflection, Activator.CreateInstance () In the way you care, DLL implements a specific interface and marks them with a specific feature.