Winforms: Namespaces like System.Web.Services are pending for port in .net Core

[gsmental]

every time when we try to port our existing application, we faces only these namesspaces which can not port into .net Core. technically these all are WebService (asmx) based libraries. i hope these will be also port into .net core

System.Web.Services.Protocols.HttpWebClientProtocol
System.Web.Services.WebServiceBindingAttribute
System.Web.Services.Protocols.WebClientProtocol
System.Web.Services.Protocols.SoapHeader
System.Web.Services.Protocols.SoapHeaderAttribute
System.Web.Services.Protocols.SoapDocumentMethodAttribute
System.Web.Services.Protocols.SoapHttpClientProtocol
System.Web.Services.Protocols.InvokeCompletedEventArgs
System.Web.Services.Protocols.SoapParameterStyle
System.Web.Services.Description.SoapBindingUse

[RussKie]

Web stuff is really outside the realms of WinForms.
Besides I don't believe WS are supported in .NET Core. IIRC there are few 3rd packages available, google is your friend.

[gsmental]

@RussKie you are right bro, google is our friend, after spending 15 years in MS, now i am thinking to move with NodeJs,Mongo,react...

[199621616]

这也是我们在迁移桌面程序时，遇到的主要问题之一。希望早日解决。

[OliaG]

@gsmental thanks for your issue. We don't support SOAP in .NET Core. You can try using WebAPI (for hosting) and HttpClient (for consumption).

cc @terrajobst

[OliaG]

For better web experience you can use ASP.NET Core. WinForms does not cover web functionality. I am going to close this issue here, but feel free to reach out to @terrajobst for more details regarding APIs in .NET Core.

[RussKie]

https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/

[TanVal]

every time when we try to port our existing application, we faces only these namesspaces which can not port into .net Core. technically these all are WebService (asmx) based libraries. i hope these will be also port into .net core

System.Web.Services.Protocols.HttpWebClientProtocol
System.Web.Services.WebServiceBindingAttribute
System.Web.Services.Protocols.WebClientProtocol
System.Web.Services.Protocols.SoapHeader
System.Web.Services.Protocols.SoapHeaderAttribute
System.Web.Services.Protocols.SoapDocumentMethodAttribute
System.Web.Services.Protocols.SoapHttpClientProtocol
System.Web.Services.Protocols.InvokeCompletedEventArgs
System.Web.Services.Protocols.SoapParameterStyle
System.Web.Services.Description.SoapBindingUse

Hi, I am also facing same issue. may I know if the issue is resolved and how was it resolved? Also please let me know how much was the effort.