Click here to Skip to main content
15,567,221 members
Articles / Programming Languages / VBScript
Posted 9 Dec 2016

Tagged as


3 bookmarked

Consume SOAP Service with COM Component

Rate me:
Please Sign up or sign in to vote.
5.00/5 (4 votes)
12 Dec 2016CPOL1 min read
This article explains how to consume a WebService (SOAP) from plain VisualBasicScript by using a COM DLL written in C#.

Sure there is a way to send a request to SOAP service "manually" by writing down a XML file and posting it to server as HTTP POST like this.

This is however a hard way, you need to handle such a complex structures like:

<?xml version=""1.0"" encoding=""utf-8""?>
<soap:Envelope xmlns:soap="""" 
<fruit:findBananasbyId><Id>" & bananaId & /Id></fruit:findBananasById></soap:Body></soap:Envelope>"

and believe me, that is just a beginning. :)

On the other side, it is very simple to create a client application to consume a SOAP service in Visual Studio. Take a look for example at this link.

Now you can create a .NET library (DLL) but how to use it from a VBS?

The answer is - the DLL need to be a COM object!

Assumed we have such a COM-DLL, we can easily use it:

Dim oComSoap
Set oComSoap = CreateObject("myComInterface")

There are certainly two points / pitfalls:

  1. The .NET WCF Application has an app.config looking like this:
    < system.serviceModel >
            < bindings >
              < wsHttpBinding >
                   < binding name = "WSHttpBinding_PurchaseInvoiceService" />
              </ wsHttpBinding >
            </ bindings >
            < client >
              < endpoint address = 
                      binding = "wsHttpBinding" 
                      bindingConfiguration = "WSHttpBinding_PurchaseInvoiceService"
                      contract = "PurchaseInvoiceService.PurchaseInvoiceService" 
                      name = "WSHttpBinding_PurchaseInvoiceService" >
                  < identity >  
                    < userPrincipalName value = "" />
                  </ identity >
              </ endpoint >
            </ client >
    </ system.serviceModel >

    Your stand-alone DLL makes no use of app.config and shall replace it by creating an according class:

    PurchaseInvoiceServiceClient _oClient;
    WSHttpBinding oBinding = new WSHttpBinding();
    oBinding.Name = "WSHttpBinding_PurchaseInvoiceService";     
    string strEndPoint = 
    EndpointAddress oEndPoint = new EndpointAddress(strEndPoint);
    _oClient = new PurchaseInvoiceServiceClient(oBinding, oEndPoint);
  2. The .NET WCF Application marks an entry point / the main function as [STAThread] that means, the COM threading model for an application is single-threaded apartment (STA).

    This is what you need to do for every SOAP interface of your DLL:

    public bool SendRequest()

Points of Interest


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By
Software Developer
Germany Germany

I'm a software developer living in Germany with my family (wife & 2 sons).
My hobbies: sport, traveling, books (former reading, now hearing).
Welcome to my homepage:

Comments and Discussions

QuestionInsane Pin
EMiller829-Dec-16 7:45
EMiller829-Dec-16 7:45 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.