Labview 7.1 integrating XML

[Ed987]

Hello,

We are currently trying to call standard XML documets / processes with Labview 7.1.  We are trying to call the XML document directly without additoinal middleware, but continue to receive the error messages below?

Could you provide some advsie or documentation on how we should proceeed with this integation?

** Note: If we upgraded to Labview version 8.2** we are able to directly connect to external XML sources with ease.  But since we have extensive amount of processes already in Labview Version 7.1 --> We would like to integrate them to realize the integration process enhansemnts sooner before we deploy Labview 8.2 world wide.

We keep getting the below error when trying to use the wsdl.  From what I understand so far, Labview has a .Net Web Services import wizard that automatically creates a dll based on the wsdl xml that I can then use in my code.  But the wizard gives the below error?

Create C# Code .vi

  Virtual Instrument

    - LabVIEW does not have references to the following .NET assemblies used by this VI:

            mscorlib, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

  Please add references to those assemblies by selecting "Tools>>Advanced>>.NET Assembly References" before editing the VI.

Generate Assembly.vi

  Virtual Instrument

    - LabVIEW does not have references to the following .NET assemblies used by this VI:

            System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

  Please add references to those assemblies by selecting "Tools>>Advanced>>.NET Assembly References" before editing the VI.

Read Service Description.vi

  Virtual Instrument

    - LabVIEW does not have references to the following .NET assemblies used by this VI:

            System.Xml, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

            System.Web.Services, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

  Please add references to those assemblies by selecting "Tools>>Advanced>>.NET Assembly References" before editing the VI.

Pleaes help with any informatoin that you may have to utilze Labview 7.1 and connect to external systems using standard XML language.

[LV_Pro]

I'm not sure about your specific problem, but in a recent project I found that there were interesting XML inconsistencies between LabVIEW 7.1 and 8.2. Specifically, files created using the older version of LabVIEW wouldn't read properly in Microsoft's xml editor, whereas those created using 8.2 (essentially the same code, just recompiled in 8.2.) would. You mention that you have a lot in 7.1. Does it not load/recompile into 8.2.1?

[tst]

---

@Ed987 wrote:

From what I understand so far, Labview has a .Net Web Services import wizard that automatically creates a dll based on the wsdl xml that I can then use in my code. 

---

Where did you see that?
Are the VIs refered to there yours or NI's?

I know that 8.2 can work with web services, but not 7.1. In 7.x, you have two requirements for using a .NET DLL - you need to place it in the same directory as the top level VI and you need to register it in Tools>>Advanced>>.NET Assembly References. The registering does nothing other than tell LV where it should take DLLs it knows about from. It can work even if you don't register.

P.S. 7.1 has a problem with .NET where you drop a constructor and it hangs. There should be a patch for that.

P.P.S. What do you mean by

We are trying to call the XML document directly without additoinal middleware

---

To me, this implies that you're trying to manipulate the string yourself or using LV's XML primitives (which won't work), but this is clearly not the case, since you're using .NET.

If you're trying to use MSXML, you can find some implementations around, like LabXML or by searching the LAVA forums.

[Wiebe@CARYA]

He's refering to the .NET Web Service Browser. This tool (you can download for free from www.ni.com) does indeed create a dll to interface with a web service. This dll uses .NET, and is created with .NET. This has little to do with XML, except the fact that web services use XML.


We tried the web service browser, but couldn't use the dll's. So we decided to manage the web service traffic ourself with TCP/IP functions, and to parse the XML files ourself (in a primitive but sufficient manner). It's not too hard, although different servers use different ways to send the data.


Regards,


Wiebe.