Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I want to connect to https://wsiinst.uni-login.dk/wsiinst-v4/ws?WSDL .

This works fine in normal .NET 4.7.

But in .NET Core 3.1, the channel is Fault, when creating the Client.. My steps..

  • create .NEt Core console App

  • Add Connected service (Microsoft WCF Web Service Reference Provider) , call it "ServiceRef"

  • Add this code to program.cs (main)

    var client= new ServiceRef.WsiInstPortTypeClient();

  • The client is created, but state is Faulted

    Perhaps web service uses something, not supported yet in core ?

    Anyone have an idea or canb point me in a direction ? :-)

    It's the same, when you add connected reference you click in other references, that you will get the service endpoint and you have to put the URI. you click GO and will get the service avaliable. If this isn't working that's mean you have a problem in the serverside. Did you bind your port correctly??

    check this link https://learn.microsoft.com/en-us/windows-server/networking/technologies/netsh/netsh-http

    after you initalize the serviveref did you open the connection?

    var client = new ServiceRef.WsiInstPortTypeClient();
    await client.OpenAsync();
    var getanobject = await client.MyobjectAsync();
                    Thanks alot m8... :-) Totally overlooked the OpenAsync, since it was not needed using regular .NET..
    – MüllerDK
                    Sep 25, 2020 at 16:28
            

    Thanks for contributing an answer to Stack Overflow!

    • Please be sure to answer the question. Provide details and share your research!

    But avoid

    • Asking for help, clarification, or responding to other answers.
    • Making statements based on opinion; back them up with references or personal experience.

    To learn more, see our tips on writing great answers.

  •