.Net DLL/WSDL Import Utility for Delphi

[CrystalNet 4]

The .Net DLL/WSDL Import Utility for Delphi is used for importing .Net assemblies as dll files, WSDL or web service XML schema and generates Delphi classes from the types of the imported assemblies.

The Import .Net Assemblies Wizard is used for importing .net assemblies and generating Delphi classes from the types of the imported assemblies.

The Import WSDL/Web Services Wizard is also used for importing Web Service Description language file/url or XML schema that describes a web service and generates Delphi classes from the types of the imported WSDL assemblies.

 

Features

• Import any .Net Libraries.
• Import any assemblies from the Global Assembly Cache (GAC).
• Import any Web Services Definition Language(WSDL).
• Uses the Host Class Library and the Framework Class library to host the .net runtime (CLR) and access the imported assemblies or WSDL without registering the .net dll as COM.

 

                                                 

 

 

For more information, go to https://crystalnet-tech.com/RuntimeLibrary/RuntimeLibUtilities.

For more information about the .Net Runtime Library for Delphi (which the .Net DLL/WSDL Import Utility for Delphi is part of), go to https://www.crystalnet-tech.com/RuntimeLibrary/RuntimeLibrary4Delphi

 

 

Edited September 20, 2019 by CrystalNet
Update images

[Ralf Kaiser 2]

When trying to import a WSDL file i get the following error on the page "WSDL Location an Soap Version":

 

 

The WSDL is not imported, no output files are generated.

 

Any hint what to do?

[CrystalNet 4]

The file you are trying to import is not a wsdl file, hence the error message. You need to specify the wsdl file with extension .wsdl or DISCOMAP file with extension .discomap together with the .xsd files if any exist. You should not import the .xsd file alone. 

[Ralf Kaiser 2]

No. I did not import a .xsd file. It was a .wsdl file that i had choosen (see screenshot). The selected file was imported by the Delphi WSDL importer before (so i can be sure that it is really a WSDL file)

 

Edited September 23, 2019 by Ralf Kaiser

[CrystalNet 4]

Sorry for the misunderstanding, can you go to the "C:\Temp" folder and move all the .xsd file extensions to a different folder and try again. I will raise this with our software engineering team to resolve this issue in the coming release but in the meantime remove the .xsd files in the same folder location as the .wsdl file to import.

 

 

[Ralf Kaiser 2]

Sorry but my folder d:\temp does not contain any *.xsd files, just a couple of text files and some xml files.

[CrystalNet 4]

I am not sure why it is behaving this way, however to help our development team debug and identify the cause of the problem and provide a resolution, can to send us a copy of the .wsdl file you want to import as an attachment via this page or via our contact link below:

https://www.crystalnet-tech.com/ContactForm.aspx

 

[Ralf Kaiser 2]

I just used several sample WSDL files from the net, for example: http://cs.au.dk/~amoeller/WWW/webservices/wsdlexample.html

[CrystalNet 4]

I am getting different error when i import the wsdl text in the link above. This error is valid.

 

 

I am having the same issue when i import via Visual studio.

 

[Ralf Kaiser 2]

You cannot import from that URL (it is just a sample and i do not think that there is a server running on "example.com"that delivers the WSDL!)

 

Just save the shown WSDL content to a file and import that file.

[CrystalNet 4]

Yes that is what I did. If you read my previous message, i imported the wsdl text in the link by copying then wsdl text and saved it to a file with extension .wsdl. You will get the above error message when you import using the utility. You will encounter the same issue if you import the saved wsdl file from Visual Studio. 

 

Can you import your wsdl file from Visual Studio using the "Add Service Reference..." menu option.?

 

Let me know of the outcome.