Module capability like a DLL?
Posted: Mon Jan 15, 2018 8:20 am
Very new to Netburner after inheriting some code after the original developer passed away.
Broad question: is there a way to do something like a windows DLL in Netburner? We have a core product functionality that doesn't change. But then there are customizations based on what the customer has purchased that require custom development.
what I would like to do is create an interface that remains constant. The main core product would call these interface commands. The baseline product would ship with a module that fleshes out these interface commands which are No Op commands. Then, if the customer has purchased extended capability, they get a different module which fleshes out the interface commands.
This way, I don't have to recompile the main code base for every customization.
Is this something that the NetBurner architecture provides for?
Broad question: is there a way to do something like a windows DLL in Netburner? We have a core product functionality that doesn't change. But then there are customizations based on what the customer has purchased that require custom development.
what I would like to do is create an interface that remains constant. The main core product would call these interface commands. The baseline product would ship with a module that fleshes out these interface commands which are No Op commands. Then, if the customer has purchased extended capability, they get a different module which fleshes out the interface commands.
This way, I don't have to recompile the main code base for every customization.
Is this something that the NetBurner architecture provides for?