New HttpRequestException.StatusCode property

[alnikola]

HttpRequestException.StatusCode property gets the HTTP status code associated with the exception if any.
It was introduced in dotnet/runtime#32455

[karelz]

@gewarren is there a way to specify that this property is new in .NET Core 5.0?
The fact it is also part of System.Net.Http is IMO not interesting.

[gewarren]

Sorry for the delay, I missed this. I left a suggestion about adding a note in the Remarks. Does that work?

[mairaw]

The Applies to section would also indicate the versions the property exists.

[gewarren]

Close/reopen to try build again.

[gewarren]

I don't understand why the build is failing. I've asked for help on the Docs support channel.

[gewarren]

@alnikola The answer from the support channel is:

"We should never manually add members to a ECMAXML file. The skeleton of a ECMAXML file should always be auto-generated by CI. If these members are meant to be there, could you please update the binaries and re-run the CI?"

Do you need @BillWagner to rerun the CI?

[alnikola]

@gewarren @BillWagner What is the standard process for skeleton regeneration? Is it normally done before each release?
I'm afraid if we rerun CI now, it will bring in not only my changes, but many others.

[alnikola]

@carlossanlop I'm waiting for a reply from @gewarren or @BillWagner to understand what is the skeleton regeneration process and if it's safe to do it now. It seems the only way to build an updated ECMAXML file with the new members I added.

[gewarren]

@mairaw , Could you weigh in here?

[mairaw]

Typically we wait until the members show up in the build automatically and then port any existing comments from the source.
I believe @BillWagner is working with @safern to get the Preview 3 assemblies in (we still have Preview 1 on the site). If this would show up later, then we need to wait.

So yeah the entire CI would bring all the changes since Preview 1 in. Then your PR could concentrate only on the new property content.

[carlossanlop]

Thanks @mairaw for replying.
@alnikola This PR is essentially blocked until we update MS Docs with the latest ref assemblies. Feel free to close it and add your changes after the API shows up in MS Docs.

[alnikola]

Closing PR until MS Docs is updated as suggested above.