VB to XBasic code conversion
============================
I don't suppose anyone has any pointers, examples, or links to this sort of
thing to help the learning curve?
Seems to me that a lot of VB/VBA devs may now be ready to tell MS 'to go forth and multiply' and start looking for alternatives. As I previously mentioned, A5 V10 seems to check all the right boxes for me, and I have a feeling this may be true for others.
Biggest problem seems to be the syntax and know-how learning curve.
I, for one, would happy to begin a regular dialog of posting info as I convert
from VB to XBasic. This mostly applies to desktop apps, but, for example:
* API calls
* WMI calls (allow building unique User IDs based on hardware)
* Methods to prevent cloned software and detect VMWare use
* Preventing other license violations
* On-the fly user activation/de-activation (great for trial/demo versions)
* Trapping public IP address and real-time blocking
For me, I don't mind sharing info and knowledge. I spent a few years with the
independent Access forums back when MS appreciated the dialog (and it was called usenet, not twitter).
If XBasic and A5 is the direction we go, it will be a commitment for several
years and I have no problem giving back. Especially since it seems to me that
the community here is kinda reminiscent of the Access community back in the day.
Many thanks in advance,
Gary
============================
I don't suppose anyone has any pointers, examples, or links to this sort of
thing to help the learning curve?
Seems to me that a lot of VB/VBA devs may now be ready to tell MS 'to go forth and multiply' and start looking for alternatives. As I previously mentioned, A5 V10 seems to check all the right boxes for me, and I have a feeling this may be true for others.
Biggest problem seems to be the syntax and know-how learning curve.
I, for one, would happy to begin a regular dialog of posting info as I convert
from VB to XBasic. This mostly applies to desktop apps, but, for example:
* API calls
* WMI calls (allow building unique User IDs based on hardware)
* Methods to prevent cloned software and detect VMWare use
* Preventing other license violations
* On-the fly user activation/de-activation (great for trial/demo versions)
* Trapping public IP address and real-time blocking
For me, I don't mind sharing info and knowledge. I spent a few years with the
independent Access forums back when MS appreciated the dialog (and it was called usenet, not twitter).
If XBasic and A5 is the direction we go, it will be a commitment for several
years and I have no problem giving back. Especially since it seems to me that
the community here is kinda reminiscent of the Access community back in the day.
Many thanks in advance,
Gary
Comment