Using MSXML Between Tiers


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: Using MSXML Between Tiers

  1. #1
    Jason Guest

    Using MSXML Between Tiers


    Does MSXML.DLL require IE to be installed? Can the dll be copied to a client
    PC, registered, and used without any dependencies on IE?

    I want to use XML to pass data between tiers in my application. The User
    Services tier (VB6) would get XML from the Business Services tier residing
    in COM+. Then the User Services tier will recreate an ADO recordset.

    VB Clients have MDAC 2.1 and do not have access to the ADODB.Stream object.
    Recordset objects need the XML parser to read XML strings/files anyway (Microsoft
    Knowledge Base Article Q198533).

    I have searched and searched but I have not found a good answer. Does MSXML.DLL
    require IE to be installed on the client machine or not? Has anyone tried
    it in an enterprise solution?

  2. #2
    Chris F. Guest

    Re: Using MSXML Between Tiers


    IE is not required. Install the MSXML 3.0 release on MSDN.

    -C


    "Jason" <Jason_Kennedy@Takata.com> wrote:
    >
    >Does MSXML.DLL require IE to be installed? Can the dll be copied to a client
    >PC, registered, and used without any dependencies on IE?
    >
    >I want to use XML to pass data between tiers in my application. The User
    >Services tier (VB6) would get XML from the Business Services tier residing
    >in COM+. Then the User Services tier will recreate an ADO recordset.
    >
    >VB Clients have MDAC 2.1 and do not have access to the ADODB.Stream object.
    > Recordset objects need the XML parser to read XML strings/files anyway

    (Microsoft
    >Knowledge Base Article Q198533).
    >
    >I have searched and searched but I have not found a good answer. Does MSXML.DLL
    >require IE to be installed on the client machine or not? Has anyone tried
    >it in an enterprise solution?



  3. #3
    B. Adji Maharyatno Guest

    Re: Using MSXML Between Tiers


    Hi Jason,

    Short answer: not necessary.

    If you want to use it as common Windows application, just use MSXML.dll supplied
    by the latest version MSXML3.dll.
    However, if you have used MSXML before version 3.0, you might need xmlinst.exe
    either to replace the current registry entries/keys or redirect them to use
    the version 3.0.

    You also can use it as usual when an ActiveX dll/exe used in VB6 (or other
    applications).

    XML DOM can be used as similiar benefit of ADODB.RecordSet. However no locking/transaction
    mechansim supported. You still can simulate the locking mechanism by creating
    small component to validate it or transform it as ADODB.Recordset.

    B. Adji Maharyatno
    Singapore



    "Jason" <Jason_Kennedy@Takata.com> wrote:
    >
    >Does MSXML.DLL require IE to be installed? Can the dll be copied to a client
    >PC, registered, and used without any dependencies on IE?
    >
    >I want to use XML to pass data between tiers in my application. The User
    >Services tier (VB6) would get XML from the Business Services tier residing
    >in COM+. Then the User Services tier will recreate an ADO recordset.
    >
    >VB Clients have MDAC 2.1 and do not have access to the ADODB.Stream object.
    > Recordset objects need the XML parser to read XML strings/files anyway

    (Microsoft
    >Knowledge Base Article Q198533).
    >
    >I have searched and searched but I have not found a good answer. Does MSXML.DLL
    >require IE to be installed on the client machine or not? Has anyone tried
    >it in an enterprise solution?



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center