Wondering if anyone has a "code" solution on how to distribute COM DLL's compiled with VB such that they can be licensed. Licensing COM objects appears to be VERY different from Licensing an ActiveX object.
To clarify, some examples are (pretty much every COM/DLL reseller on the planet like XceedSoft, WeOnlyDo, etc).
Object works like this:
License / Key can be purchased from Said company, so it is something that can be generated server side.
Object has a function called .License() which accepts one or two parameters (depending on system) which are "Name" and "License Key" or just "License Key"
Upon successful call of this ONCE (and then you can remove it from your code), the component is then licensed to the developers PC permanently.
After which, any projects the developer adds the component to, can be compiled and distributed without ever calling the .License function again, and without any trial messages/etc on the client side.
If however, the .License function was NEVER called, then all distributions will then show the "trial" message on the developer PC AND on all client machines the component was distributed to.
Now, for whatever reason, what should have an abundant source of documentation, seems to be a complete mystery and/or closely guarded secret. I am thinking NOW that VB6 is officially no longer in distribution, that someone who has EVER implemented a license mechanism (NOT Wrapper code like SoftLocx, etc) would be so kind as to cough up the details --- PLEASE!!!