Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vs 2017 wcf reference error #2327

Closed
fluppyBot opened this issue Oct 3, 2017 · 7 comments
Closed

Vs 2017 wcf reference error #2327

fluppyBot opened this issue Oct 3, 2017 · 7 comments
Assignees
Labels
tooling An issues related to any tool shipped from this repo.
Milestone

Comments

@fluppyBot
Copy link

Hi,

We have a project of asp.net core 2.0 trying to add a wcf service but was getting an error like this below
image
Would like to ask if there is possible solution for the said error? Tried to add the wcf service to asp.net mvc lower version and seems to be working fine.

Thanks,
Jordan

@hongdai
Copy link
Contributor

hongdai commented Oct 3, 2017

@fluppyBot Sorry to hear that you are running into an issue!

It looks like the service schema does not have any binding .NET Core currently support.

Could you clarify "add the wcf service to asp.net mvc lower version and seems to be working fine."? Specifically what version of asp.net mvc works?

Thanks,
Hong Dai

@hongdai hongdai added Community tooling An issues related to any tool shipped from this repo. labels Oct 3, 2017
@fluppyBot
Copy link
Author

Hi @hongdai ,

It looks like the service schema does not have any binding .NET Core currently support.
Regarding the schema not that sure because it was not created by us, in case is there a possible work around that we may try?

Could you clarify "add the wcf service to asp.net mvc lower version and seems to be working fine."? Specifically what version of asp.net mvc works?
Tried it on asp.net mvc4 and it was successful on adding the service reference and I tried it as well on asp.net web forms. Currently using the vs 2017 community edition and the latest I believe version of the wcf reference provider.

Thanks and kind regards,
Jordan

@hongdai
Copy link
Contributor

hongdai commented Oct 3, 2017

@fluppyBot
Unfortunately there is not a workaround in the case of no supported bindings.

I do not think it could work on lower version of .Net Core projects.

By asp.net mvc4, is it full framework or .Net Core? The WCF tool you used was from Add Service Reference or Connected Service? Maybe it's easier if you could give me a screenshot or detailed steps which project template was used and how the WCF reference was added.

Thanks,
Hong Dai

@zhenlan zhenlan added this to the S125 milestone Oct 3, 2017
@hongdai
Copy link
Contributor

hongdai commented Oct 3, 2017

@fluppyBot My understanding is asp.net mvc4 is full framework. So you must have used "Add Service Reference". Could you share the generated proxy code and what's added to the app.config? It will help us identify the root cause.

Thanks,
Hong Dai

@fluppyBot
Copy link
Author

Hi @hongdai ,

Tried adding it to asp.net mvc 4 web application via "add service reference"
below is the web config code that have been added

<system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="BasicHttpBinding_IFrontDesk">
          <security mode="TransportWithMessageCredential" />
        </binding>
      </basicHttpBinding>
    </bindings>
    <client>
      <endpoint address="https://services.phunkey.com/FrontDesk.svc"
        binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IFrontDesk"
        contract="ServiceReference1.IFrontDesk" name="BasicHttpBinding_IFrontDesk" />
    </client>
  </system.serviceModel>

Thanks and kind regards,
Jordan

@hongdai
Copy link
Contributor

hongdai commented Oct 4, 2017

Hi Jordan,
Unfortunately we cannot support TransportWithMessageCredential as it depends on the Message Security feature that is not yet supported in runtime. Please refer to 2.0 release notes:
Message level security is not supported (#3, #4, #8)

Thanks,
Hong Dai

@fluppyBot
Copy link
Author

Hi @hongdai ,

Seems we will not be able to use asp.net core 2.0, but anyway thanks for the help and info. :)

Kind regards,
Jordan

@hongdai hongdai closed this as completed Oct 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling An issues related to any tool shipped from this repo.
Projects
None yet
Development

No branches or pull requests

3 participants