Thanks for your nice words & review.
The idea is very simple & is part of my xNeat project @ www.xneat.com
Simply i wrote another wscript.exe ( wscript.exe execute vbs files under
windows ) and instead of passing the script file as argument to wscript.exe ,
it is embedded in the exe itself as a recourse.
And the recourse itself is encrypted using 128 key.
Also i exposed a COM object named xnHost, through which you can call win32
API . i take the argument then call LoadLibrary API .. etc.
Another point you mentioned, how you can make sure the result EXE doesn't
contains anything harmful. actually i can find nothing but my words that it
doesn't !, the same as any freeware utility you download. how can you make
sure it doesn't contain any ?!
another point, how the exe is generated. i have exe template on server. i
read it update the recourse then encrypt it ( very simple )
Anyway, i am working now on adding JScript & HTML support. so you can
convert any html, css, jscript, vbscript to exe.
Now comes a Qes: why all this ?
for me i did so because, i HATE the gui coding using c#, vc++ very boring.
so currently i wrote my core applications as dlls and my GUI using HTML &
JScript ( with the ability to call win32 API from jscript, which mean i can
call my dlls easily ).
for others there still a lot:
1- if you want to call win32API no need to use dynacall.dll which require
COM registration and means extra dll beside your vbs. also dynacall doesn't
support win32 Struct.
2- hide / encrypt your vbs files ( i have a friend of mine who liked vbs2exe
a lot since he will be able to encrypt the vbs files before he deliver them
to his clients.(he works in deploying management system )
3- if you write your application using .hta, you will have a lot of warnings
especially if you run it under windows Vista, vbs2exe doesn't suffer from
That is all :)
I am open to any questions.
Thanks mr_unreliable & i hope my answer is detailed enough.