Skip navigation

Rem: Dispelling Some Misinformation About CScript

I hope you'll forgive me for attending Microsoft Certified Professional Magazine's "Network Scripting Workshop" rather than The Scripting Guys workshop at the Windows & .NET Magazine Connections conference. You know what they say: "Live and learn." Anyway, the instructor mentioned that Microsoft might be getting rid of CScript, which would cause me and the other network guys at my company major grief because we use CScript far more than WScript. We configure CScript as the default script host on all our servers and workstations. Is CScript going away?

I don't know where your instructor got his or her information, but I think you're safe with CScript for the foreseeable future. Getting rid of CScript, but not WScript, just doesn't make sense. However, if you're looking for more tangible evidence, look no further than the new script-based command-line tools included with Windows Server 2003. Take the eventquery.vbs utility, for example. You must run eventquery.vbs with CScript because of the volume of data the utility is capable of returning. The same is true for many other Microsoft scripts. I think you're heading down the right path by going with CScript. And if there's a significant change to Microsoft's scripting story, I'd be willing to bet you'll get accurate facts here.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.