LPX6 requirement for .NET Core breaks WCF/Soap Connection Drivers

ericwu91

The new LPX file requires that the driver compiles against .NET Core; However, on drivers that attempt to read WSDL files through the System.Web.Services library (e.g. https://github.com/dylanmei/linqpad-soap-driver) won't work anymore, since it simply does not exist in this environment.

Are there any ideas on how to implement it to work in Linqpad6+ ?

JoeAlbahari

That's right: LINQPad 6 runs under .NET Core, so any drivers for LINQPad 6 must also run under .NET Core.

So to get this to work, you would need to write a separate driver for LINQPad 6, or a driver that dual-targets .NET Core and .NET Framework. Writing a separate driver is probably a better option because there are structural differences in how you would go about supporting SOAP in .NET Core (due to WCF not being a part of .NET Core):

https://github.com/dotnet/wcf

https://medium.com/grensesnittet/integrating-with-soap-web-services-in-net-core-adebfad173fb

The process of writing a LINQPad driver is documented here:

https://www.linqpad.net/Extensibility.aspx

ericwu91

Having searched the entirety of the WCF source, as well as the ReferenceSource, the only option I could sanely come up with was calling `dotnet-svcutil` in the "Connect" button click. Is it possible?
I know it requires .Net Core SDK to exist in the running environment.

JoeAlbahari

I believe what this does is to call Tool.Main in %userprofile%\.nuget\packages\dotnet-svcutil\2.0.1\tools\netcoreapp2.1\any\dotnet-svcutil-lib.dll.

You might be able to call this directly if you can find a way to automate the installation of the dotnet-svcutil NuGet package. If you cannot, an option might be to re-publish that package as a library rather than a tools package so that you can reference it.

ericwu91

Hmmm interesting. I found the nuget package for donet-svcutil, so referencing it in the driver might be worth a try.

I'll come back with news.

Thanks for now!


Now I understood what you said here.

JoeAlbahari said:

If you cannot, an option might be to re-publish that package as a library rather than a tools package so that you can reference it.

Do you happen to a source somewhere to point me where to start?

JoeAlbahari

I think if you move the contents of the tools folder into the lib folder, you should get most of the way there.

lib\netcoreapp2.1\dotnet-svcutil-lib.dll + dependencies

https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package

ericwu91

Thanks, I'll give it a try!

falthazar

Did you have any luck with this?

ericwu91

@falthazar , no. I forked dylanmei's project, but ran into a few issues, so I froze it. Might consider coming back to it, if enough people join to help me