Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reopen #2295 - Message Header not scaffolded via Connected Service (not enabled for net45x)

See original GitHub issue

Please reopen #2295 - this issue is not resolved. See latest comments on that item.

Simply put - in a current ASP.Net App using VS 2017 and current tooling by adding “Connected Service” when you scaffold this service: https://pe-96.praceng.us/reports/perepgen.asmx - You should get an attribute like this scaffolded:

[System.ServiceModel.MessageHeaderAttribute(Namespace = "http://www.praceng.com/webservices/perepgen")]
        public RepGen96.AuthenticationInformation AuthenticationInformation;

however you don’t.

Issue Analytics

State:
Created 6 years ago
Comments:11 (7 by maintainers)

Top GitHub Comments

1reaction

zhenlancommented, Feb 22, 2018

@rposener, glad you made it work.

Types like EndpointAddress and BasicHttpBinding ARE available on .NET Core. Please make sure you do package restore before using them.

Let’s keep this thread for the original issue. Please open new issues for anything new.

1reaction

zhenlancommented, Feb 15, 2018

We have logic in the connected service tool to create different code based on the availability of features in different versions of frameworks. Right now, the message header feature is injected when a project targets netcoreapp2.0, netstandard2.0 or later (this is fixed as part of #2295). @mlacouture, I think we should include net45x or later here too.

@rposener as a workarond, is it possible for you to change your target framework to netcoreapp2.0 temporarily and get proxy code generated? Then you can change the target framework back.