Migrate .netcore 2.2 to .netcore 3.1

Question

0.00/5 (No votes)

See more:

When I migrate .NetCore 2.2 to .NetCore 3.1 I got below error

DefaultHttpRequest - Microsoft.AspNetCore.Http.Internal - .NetCore 2.2

DefaultHttpRequest - Not found in .NetCore 3.1

What I have tried:

I have migrated .NetCore 2.2 to .NetCore 3.1

Posted 29-Jan-20 6:33am

Mohammad Nawaz

Updated 29-Jan-20 7:43am

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2020-01-29T06:49:00

Solution 1

Read: Breaking changes, version 2.2 to 3.1 - .NET Core | Microsoft Docs[^]

Various classes have been moved around or replaced as .Net Core, ASP.NET Core, and EF Core matures.

Posted 29-Jan-20 6:49am

Dave Kreskowiak

Comments

Mohammad Nawaz 29-Jan-20 13:36pm

@Dave Kreskowiak, Please help me to solve this issue as i am unable to do that, i have already check docs you have provided but doesn't "DefaultHttpRequest"

Dave Kreskowiak 29-Jan-20 15:58pm

I couldn't tell you. I don't have any examples to work with nor the time to generate one. But since they recommended replacing DefaultHttpContext with HttpContext, I would first try the same thing with HttpRequest.

Richard MacCutchan · Answer 2 · 2020-01-29T07:44:00

Solution 2

Breaking changes, version 2.2 to 3.1#http-defaulthttpcontext-extensibility-removed[^]

Posted 29-Jan-20 7:44am

Richard MacCutchan

Updated 29-Jan-20 7:45am

v2

Comments

Mohammad Nawaz 29-Jan-20 13:50pm

It is for DefaultHttpContext but my class is DefaultHttpRequest

Richard MacCutchan 30-Jan-20 4:50am

Sorry, I misread the question.