7

Can somebody please guide me in the right direction of creating a scripting language that targets the WSH (Windows Scripting Host)?

I have googled for it, but there seem to be far fewer links related to this than when I originally searched for it a few months back.

THank you

Earlz
  • 62,085
  • 98
  • 303
  • 499
  • You may be better off building on PowerShell. You get so much more for free. You haven't told us what your purpose is, so who knows? – Jay Bazuzi Mar 13 '10 at 22:17
  • Duplicate: http://stackoverflow.com/questions/174240/writing-a-language-for-the-windows-scripting-host-wsh – Helen Mar 14 '10 at 10:44
  • 1
    This should not be marked as a duplicate. Since I was dissatisfied with the answers given for question 174240. –  Mar 14 '10 at 11:46
  • 2
    @j-t-s, it might be worth indicating what you felt was missing from those answers so that people can provide you with the information you were looking for – Dancrumb Mar 16 '10 at 14:22

3 Answers3

1

The product is now called "Windows Script Host". The MSDN documentation suggests that what you want is a Windows Script Engine, about which the documentation claims that you can create one for any programming language or environment—presumably including one you create yourself. Beyond that, the documentation is not terribly clear.

Norman Ramsey
  • 198,648
  • 61
  • 360
  • 533
0

You should be able to find all necessary information about creating Windows Script engines on MSDN; other than that there seems to be no resources available (at least I couldn't find any). You can also take a look at some open-source engine implementations to get the idea of what your code should look like:

If you have any specific questions about implementing Windows Script interfaces, feel free to ask them here. Good luck!

Helen
  • 87,344
  • 17
  • 243
  • 314
0

Topic starter need to carefully read the script56.chm, which can be found on MSDN. This help file describes WSH engine specification.

Himanshu
  • 31,810
  • 31
  • 111
  • 133
Sergey
  • 1