Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
encrypting / licensing a script
12 views
Skip to first unread message
adamchapman
Oct 21, 2012, 9:32:21 AM10/21/12
to
I have written a VB script to run as a macro add-on to another piece of software.
It has to be saved with a file extension ".m1s" to work in the environment.
Is there any way I can encrypt and eventually licence this script?
Perhaps I could make the ".mls" script call an encrypted vb script - if I did, would variables still be passed into the host software?
It has to be saved with a file extension ".m1s" to work in the environment.
Is there any way I can encrypt and eventually licence this script?
Perhaps I could make the ".mls" script call an encrypted vb script - if I did, would variables still be passed into the host software?
Mayayana
Oct 21, 2012, 9:46:30 AM10/21/12
to
VB and VBScript are entirely different things.
For VBS you want:
microsoft.public.scripting.vbscript
There's an MS encrypter for VBS that turns out
.vbe files, but they're fairly easily decrypted. There
are also programs that claim to turn VBS files into
EXEs. But the long and the short of it is that script
is plain text, so you're going to have a hard time
trying to sell script software. And to attempt
encryption is to lose the advantages (transparencey,
editability) of script while keeping the disadvantages
of dependencies and low efficiency.
--
--
"adamchapman" <adamcha...@hotmail.co.uk> wrote in message
news:f565fbf0-7077-471c...@googlegroups.com...
For VBS you want:
microsoft.public.scripting.vbscript
There's an MS encrypter for VBS that turns out
.vbe files, but they're fairly easily decrypted. There
are also programs that claim to turn VBS files into
EXEs. But the long and the short of it is that script
is plain text, so you're going to have a hard time
trying to sell script software. And to attempt
encryption is to lose the advantages (transparencey,
editability) of script while keeping the disadvantages
of dependencies and low efficiency.
--
--
"adamchapman" <adamcha...@hotmail.co.uk> wrote in message
news:f565fbf0-7077-471c...@googlegroups.com...
Auric__
Oct 21, 2012, 11:37:01 AM10/21/12
to
Mayayana wrote:
> VB and VBScript are entirely different things.
> For VBS you want:
>
> microsoft.public.scripting.vbscript
>
> There's an MS encrypter for VBS that turns out
> .vbe files, but they're fairly easily decrypted. There
> are also programs that claim to turn VBS files into
> EXEs. But the long and the short of it is that script
> is plain text, so you're going to have a hard time
> trying to sell script software. And to attempt
> encryption is to lose the advantages (transparencey,
> editability) of script while keeping the disadvantages
> of dependencies and low efficiency.
ISTR that some (many? most?) VBscripts can be handled by VB simply by adding
> VB and VBScript are entirely different things.
> For VBS you want:
>
> microsoft.public.scripting.vbscript
>
> There's an MS encrypter for VBS that turns out
> .vbe files, but they're fairly easily decrypted. There
> are also programs that claim to turn VBS files into
> EXEs. But the long and the short of it is that script
> is plain text, so you're going to have a hard time
> trying to sell script software. And to attempt
> encryption is to lose the advantages (transparencey,
> editability) of script while keeping the disadvantages
> of dependencies and low efficiency.
a reference to the VBscript runtime and making some fairly simple changes to
the code.
If I was in the OP's shoes, I'd write my add-on in a "normal" compilable
language, roll it into a DLL, and call that from the VBscript (if such a
thing is possible in your chosen environment).
--
Archie Comics:
Come for the humor and romance and stay for the knife fights.
0 new messages