Unable to create web reference for WSDL file

Question

I've created an ASP.Net core 3.1 project with Visual Studio 2019. I want to add a WSDL service as a web reference. But I can't. Why the Advanced button removed in this form.

Visual Studio 2019:

Old version:

I've read somewhere that, Web reference is deprecated. How can I do it?

UPDATE1: The errors of documentation example code when I added it as a service reference

In the documentation of the service mentioned, I should add it as a `web reference`. When I add it as a `service reference`, the documentation sample code doesn't work. — Saeid Amini, Oct 04 '20 at 15:14
Adding it as `service reference` seems to work - what is exactly the problem you encounter? — Stefan, Oct 04 '20 at 15:32
The documentation has many examples. When I add the service as a `service reference` those examples don't work. https://stackoverflow.com/questions/2158106/web-reference-vs-service-reference — Saeid Amini, Oct 04 '20 at 15:39
Don't work can be due to a lot of things. We need details like error information, stacktraces etc. — Stefan, Oct 04 '20 at 15:43
There is no error. Is adds to the project successfully. But it seems the `service reference` and `web reference` are different(different interfaces). — Saeid Amini, Oct 04 '20 at 15:52
You are saying it does not work? What is it that doesn't work? — Stefan, Oct 04 '20 at 15:56
I said, "The documentation has many examples. When I add the service as a service reference those examples don't work." But it successfully adds. There is no error to add. — Saeid Amini, Oct 04 '20 at 16:26
My main question is not why my codes don't work. My question is how can I add the WSDL as a `web reference`. — Saeid Amini, Oct 04 '20 at 16:33
There is no difference between them: it creates a client library - that's all that matters. — Stefan, Oct 04 '20 at 16:34

Stefan · Answer 1 · 2020-10-04T16:52:43.133

You just should use the new method. The old one is deprecated - see the question in your comment: Web Reference vs. Service Reference.

The last answers sums it like it is. In the end, the reference is just the creation of a client library to call the service. That's it.

Adding a service reference allows you to create a WCF client, which can be used to talk to a regular web service provided you use the appropriate binding. Adding a web reference will allow you to create only a web service (i.e., SOAP) reference.

If you are absolutely certain you are not ready for WCF (really don't know why) then you should create a regular web service reference.

(see: https://stackoverflow.com/a/2158137/2416958)

So, to "fix" your issue:

You need to include the namespace which you used to create the client on top of your file:

In my example:

using ServiceReference1;

But it can be different in your case. You can find it at the generated files, its called ServiceReference1 in my case:

//------------------------------------------------------------------------------
// <auto-generated>
//     This code was generated by a tool.
//
//     Changes to this file may cause incorrect behavior and will be lost if
//     the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace ServiceReference1
{
    
    
    [System.CodeDom.Compiler.GeneratedCodeAttribute("Microsoft.Tools.ServiceModel.Svcutil", "2.0.1")]
    [System.ServiceModel.ServiceContractAttribute(Namespace="webservice.magfa.com", ConfigurationName="ServiceReference1.MagfaSoapServer")]
    public interface MagfaSoapServer
    {

You need to create a new one with this:

var client = new MagfaSoapServerClient();
client.ClientCredentials = ...

Unable to create web reference for WSDL file

1 Answers1