C#•2y ago

Migrating WSDL imports via ServiceDescriptionImporter from Framework to Core

I'm writing documentation website for a backwards compatible API. I'm migrating code from .NET Framework 4.7.2, to .NET8.

In

net472

net472

, we get the results of any given WSDL URL, read it into a

System.Web.Services.Description.ServiceDescription

System.Web.Services.Description.ServiceDescription

, check if there are any warnings with a

System.Web.Services.Description.ServiceDescriptionImporter

System.Web.Services.Description.ServiceDescriptionImporter

, create an assembly in memory, with

Microsoft.CSharp.CSharpCodeProvider

Microsoft.CSharp.CSharpCodeProvider

, and then read the

System.Type

System.Type

from the assembly via reflection.

A lot of this has been ripped out of BCL in Core. Both SOAP and WCF are both depreciated, but a lot of our clients still use the SOAP services on legacy projects; so we need to keep them up, and documented. But, we also need to move on tech-stack wise. So, I'm wondering what the options are. Ideally, some wonderful person will have created a NuGet library that would wrap all of this up, and make it all magically work within

net8.0

net8.0

. But, failing the coming of a saviour, how else would it be possible to programmatically resolve a

System.Type

System.Type

from any given WSDL URL?

TeBeCo•4/11/24, 5:33 PM

the Client for WCF still exists

TeBeCo•4/11/24, 5:33 PM

the server for WCF is now a community maintained open source, it's named IIRC

TeBeCo•4/11/24, 5:34 PM

so i would honnestly start with that for the migration

TeBeCo•4/11/24, 5:34 PM

Client migration => use the new WCF Client compliant with net core

TeBeCo•4/11/24, 5:35 PM

Server migration => use WCFCore that is OpenSource / community made and is net core compatible

TeBeCo•4/11/24, 5:35 PM

then from that make a migration road map

TeBeCo•4/11/24, 5:35 PM

disregard anyform of diving into the CSharpCodeProvider and anything

TeBeCo•4/11/24, 5:35 PM

i would create a new project with new stack

TeBeCo•4/11/24, 5:35 PM

and aim to target that

TeBeCo•4/11/24, 5:36 PM

ie: by removing package and class probably or completly redoing some part of the code if there's no equivalent or completly different way

TeBeCo•4/11/24, 5:36 PM

trying to bend something that isn't made to bend will break

TeBeCo•4/11/24, 5:37 PM

an general easy migration path is to tell customer to create a fulliy new client or fully new server

TeBeCo•4/11/24, 5:37 PM

and start from the contract ONLY

ApacheOP•4/11/24, 5:37 PM

The services themselves are not being touched. All I'm doing is migrating the API reference docs, from Umbraco, to OrchardCore, with a Blazor de-coupled front-end.

TeBeCo•4/11/24, 5:37 PM

and then bind the existing code

ApacheOP•4/11/24, 5:38 PM

The reference docs have code samples, and live demos. The live demos can use REST, that's fine.

TeBeCo•4/11/24, 5:38 PM

ok ok

ApacheOP•4/11/24, 5:38 PM

But the code samples are programmatically built from the SOAP objects.

ApacheOP•4/11/24, 5:46 PM

There's a NuGet package, but it doesn't contain , only .

TeBeCo•4/11/24, 5:47 PM

i don't know how to solve you're problem

TeBeCo•4/11/24, 5:48 PM

the 2 stack forked

TeBeCo•4/11/24, 5:48 PM

you're asking the new one ot generate docs sample like the old one was doing

TeBeCo•4/11/24, 5:48 PM

i just don't know

TeBeCo•4/11/24, 5:48 PM

espeically if the actual production code stay old stack and client also stay old stack

TeBeCo•4/11/24, 5:48 PM

I would continue to generate stuff from old stack

TeBeCo•4/11/24, 5:48 PM

and incorporate that

TeBeCo•4/11/24, 5:49 PM

no clue

TeBeCo•4/11/24, 5:49 PM

¯\_(ツ)_/¯

reflectronic•4/11/24, 8:29 PM

so… the code for ServiceDescriptionImporter is online and licensed appropriately for use https://github.com/microsoft/referencesource/blob/master/System.Web.Services/System/Web/Services/Description/ServiceDescriptionImporter.cs

reflectronic•4/11/24, 8:30 PM

i haven’t looked to see how much the implementation relies on internal classes to WCF

reflectronic•4/11/24, 8:30 PM

if it doesn’t, then you can just copy it into your project

reflectronic•4/11/24, 8:31 PM

if it does, you’ll have to fork WCF, add the code in, and build a private version of System.ServiceModel.* to use

ApacheOP•4/11/24, 8:47 PM

The answer to this question is pretty much exactly what we are doing now, and need to move away from:

https://stackoverflow.com/questions/38482849/generating-proxy-class-from-wsdl-on-the-fly

Stack Overflow

Generating proxy class from WSDL on the fly?

I'm currently working a Windows Service which when started takes a load of scripts and compiles them for running on a schedule, however some of these scripts need to access ASMX web services.

My