System.Web namespace vs .net core

[rhires]

Summary

It's not a bug as much as a deep need. The System.Web namespace from ASP.NET is gone, and the individual replacements for the various things under it aren't documented for what replaces them in .net core. We need a document or something to explain what the replacement namespaces are.

Motivation and goals

1-2 paragraphs, or a bullet-pointed list. What existing pain points does this solve? What evidence shows it's valuable to solve this?

In scope

A list of major scenarios, perhaps in priority order.

Out of scope

Scenarios you explicitly want to exclude.

Risks / unknowns

How might developers misinterpret/misuse this? How might implementing it restrict us from other enhancements in the future? Also list any perf/security/correctness concerns.

Examples

Give brief examples of possible developer experiences (e.g., code they would write).

Don't be deeply concerned with how it would be implemented yet. Your examples could even be from other technology stacks.

[sunandabalu]

@mjrousos should have some helpful pointers here.

[mjrousos]

Hi @rhires, I agree this is a space where more guidance is needed. I think ideally Upgrade Assistant would automatically replace some of those System.Web APIs (the ones with straightforward replacements) and alert the user (via warnings during execution and in a report afterwards) of other APIs that will need replaced manually.

Epic #55 is tracking work items related to implementing those sorts of analyzers and code fix providers. It's just a matter of getting them implemented.