Encoding Source

Script Encoder is a simple command-line tool that enables script designers to encode their final script so that Web hosts and Web clients cannot view or modify their source. Note that this encoding only prevents casual viewing of your code; it will not prevent the determined hacker from seeing what you've done and how.

Web designers use scripting on Web pages and server-side active server pages (.ASP) to add virtually every kind of feature you can imagine. In addition, scripting is used by the Windows® Scripting Host (WSH) and in a number of other applications with equally impressive results.

Up to now, one of the shortcomings of using scripts is that they afford no protection of the intellectual property contained within, nor do they provide any assurance that what users get is what you created. Clever algorithms and carefully designed scripts were always completely visible because they were stored as plain text. As a result, script users at every level could see the script designer's code and could then take it, modify it, and make it their own. Obviously, this is not good if you're trying to get an edge in a very competitive environment.

With the introduction of scriptlets, protecting the source code becomes even more important. Script designers want to use this simple component architecture, but they don't necessarily want to share their source code with the world. After a script is encoded, changing any part of the resulting file will render it inoperable, thus ensuring the absolute integrity of your encoded script.

http://msdn.microsoft.com/downloads/

Good answer 3B but remember that a DETERMINED AND SAVVY person could try using something like this to unencode something generated by the Windows Script Encoder:

http://www.klaphek.nl/nr6/scrdec.html

Actually... let me develope my previous post - why do we need this protection. We just want to secure our future incomes from this client. This is our small insurance, that client will not hire someone for $8/hr to add something to application, or even modify it and sell to someone else. If he will need to unencode it he will need professional, who asks $50-100/hr, but in this case he can just call us back :)))

Bluefrog, I tried it once with one of my clients - www.wheelchair.com and it worked just perfect without any DLLs. So, I guess since I use standard Microsoft encoding and site is running on Microsoft' ASP they use same program to unencode all scripts before executing them.

So, 2 things I know for sure - such thing as encoding exist and it works fine.