FIX: ScriptControl Reports Invalid Language for VBScript in MFC

RESOLUTION

• Clear the language before setting it:
  
  Add a call to ScriptControl::SetLanguage(NULL) right before calling ScriptControl::SetLanguage("VBScript").
• Automating the ScriptControl object:
  
  Alternatively, applications that use the ScriptControl can switch to automating the Script Control just as an automation object rather than as a full-blown control. This has the advantage of resolving the bug indicated by this article as well as improving performance. The client application does not need to go through the overhead of the ActiveX control hosting negotiation, which is essentially unnecessary for the non-UI Script Control.

Sample Code

// Import Type Info from Script OCX - point path to the
// location of the Script Control on your development computer.
#import "C:\Program Files\Microsoft Script Control\msscript.ocx"

void CScrptctrlView::OnInitialUpdate()
{
   CView::OnInitialUpdate();

   OleInitialize(NULL); // Only if you haven't done this already
                        // or called AfxOleInit.
   using namespace MSScriptControl;
   try  // Make sure exception handling is turned on.
   {
      _bstr_t bstrLanguage(L"VBScript");
      _bstr_t bstrCode(L"MsgBox \"Hello World\"");

      // Create the Script Control, initialize Language, and
      // add code for processing.
      IScriptControlPtr spScriptCtl(__uuidof(ScriptControl));
      spScriptCtl->put_Language(bstrLanguage);
      spScriptCtl->AddCode(bstrCode);
   }
   catch(_com_error e)
   {
      TRACE(_T("Error (%08x) in %s: %s\n"), e.Error(),
                           e.Source(), e.Description());
   }
}