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

System.Web is not available on Core 2.0 #838

Closed
pardhumeduri opened this issue Aug 15, 2017 · 7 comments
Closed

System.Web is not available on Core 2.0 #838

pardhumeduri opened this issue Aug 15, 2017 · 7 comments

Comments

@pardhumeduri
Copy link

we are using VS2017 15.3 preview 7 and while referring the .Netframework 4.5.1 dll / nuget package in core 2.0 application , we are getting "System.IO.FileNotFoundException: 'Could not load file or assembly 'System.Web.Services, Version=4.0.0.0, "

old application was using .net framework 4.5.1 which is a class library and has System.Web.Services name space for manage soap exceptions.

Kindly help.

@pardhumeduri pardhumeduri changed the title Deprecated Namespace issue in Core Deprecated Namespace issue in Core 2.0 Aug 15, 2017
@karelz
Copy link
Member

karelz commented Aug 22, 2017

System.Web is not part of .NET Core: https://apisof.net/catalog/System.Web.Services

@roozbehid-ic
Copy link

@karelz Is there a plan to port it? It seems Xamarin already has it, so shouldn't be that hard to port it to different oses?

@Petermarcu
Copy link
Member

@DamianEdwards to speak to any plans to port any part of System.Web.

@DamianEdwards
Copy link
Member

There is no plan to port any part of System.Web to .NET Core. Can you explain more of what the class library is doing so that we might recommend some different approaches?

@Petermarcu Petermarcu changed the title Deprecated Namespace issue in Core 2.0 System.Web is not available on Core 2.0 Oct 6, 2017
@richlander
Copy link
Member

I'd suggest running API Port on your codebase so that we can get a better sense of your dependencies. Our API Catalog claims that we have no API Port information for these types.

I'm assuming that these soap exceptions are produced on the server. Yes? We don't have a SOAP server implementation on .NET Core. What would this code do in absence of that?

@Petermarcu
Copy link
Member

@richlander, should we move this to corefx or to an aspnet repo so its better on the radar?

@Petermarcu
Copy link
Member

Ok, at this point @DamianEdwards has confirmed this is not on the asp.net team's roadmap. If you want to have more discussion on this, I'd suggest opening an issue on the aspnet/home repo. I"m going to close this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants