The WSDL has 2 malformed elements. It has been a long time since I did a SOAP based integration, but as I remember the MXBoolean does not generate correctly. Fortunately, you can manually fix those two elements safely and then allow VS to create your stub for you.
If you have the actual error and sample WSDL files I can probably provide the fix for you. I used to have this on hand, but like I said, it has been a decade since I last encountered this.
Jason
------------------------------
Jason VenHuizen
https://sharptree.iohttps://opqo.io------------------------------
Original Message:
Sent: Mon October 31, 2022 05:42 PM
From: Tim Singline
Subject: Web Services via Visual Studio 2019
We have a consultant that is trying to develop a C# application to update a Maximo Web Service using Visual Studio 2019.
When he tries to add the WSDL as a resource it fails to load 2 type definitions and the app won't compile.
We are on Maximo (MIF) 7.6.1.2.
Has anyone experienced similar issues trying to access Maximo Web Services from VS2019?
Tim Singline
Digital Delivery, Technical Lead
D (03) 6333 9320
M 0407 578 675
F 1300 862 066
A GPO Box 1393, Hobart TAS 7001
36-42 Charles Street, Launceston, TAS 7250
E tim.singline@taswater.com.au
W http://www.taswater.com.au/
Have I been helpful? Please provide feedback by clicking here.
Disclaimer
This email, including any attachments, may be confidential and/or legally privileged. You must not use, access or disclose it other than for the purpose for which it was sent. If you receive this message or any attachments or information in it in error, please destroy and delete all copies and notify the sender immediately by return email or by contacting TasWater by telephone on 136992. You must not use, interfere with, disclose, copy or retain this email. TasWater will not accept liability for any errors, omissions, viruses, loss and/or damage arising from using, opening or transmitting this email
#AssetandFacilitiesManagement
#Maximo