Create pages documenting .NET SDK error messages

[tdykstra]

An example of a .NET SDK error is NETSDK1045.

Follow pattern of C# compiler error docs

High-traffic errors (# of F1 queries from VS)

• NETSDK1045
• NETSDK1004
• NETSDK1064
• NETSDK1079
• NETSDK1071
• NETSDK1005
• NETSDK1080
• NETSDK1022
• NETSDK1073
• NETSDK1013
• NETSDK1138
• NETSDK1137
• NETSDK1136
• NETSDK1141
• NETSDK1130
• NETSDK1112

Periodically review traffic statistics and document additional error numbers.

[adegeo]

Do we want to automate the creation of each file and basic structure?

[tdykstra]

I was thinking we would create a stub file and each time a page is created it would start by copying the stub Markdown. Do you have a better idea?

[adegeo]

That sounds good. Can just use some powershell to load the xml file and for each data/value combo extract the error code and description and fill it in the copied file.

[tdykstra]

As long as it works selectively one by one, as we don't need to create pages for all of the errors, only those that require more explanation than the message itself conveys.

[adegeo]

We wouldn't want them all? If someone uses the error lookup in visual studio, where would it go for a missing error?

[tdykstra]

We could create one doc that lists all error numbers for which we decided additional information is not needed.

[marcpopMSFT]

I had originally assumed we'd have one doc with all the items in a table but I see that compiler errors and CA warnings are all separate documents so we'd be matching that existing experience. Note that we may not have a lot of extra detail for many of them beyond what's in the message (as hopefully most of the messages are enough).

[ghogen]

@tdykstra @adegeo @marcpopMSFT Some of these are still impacting our VS hub page, most significantly NETSDK1045 and NETSDK1004, which rank among the top 25 incoming F1 queries in the VS docs.

For NETSDK1045, I see a StackOverflow article that is currently popular, which could potentially be used as inspiration for an article. https://stackoverflow.com/questions/55741953/getting-netsdk1045-the-current-net-sdk-does-not-support-net-core-3-0-as-a-tar

NETSDK1004 seems to be about a missing assets file, but that could have many causes. I'd be in favor of adding the article here to capture the F1 traffic, even if it's fairly short and simple. https://stackoverflow.com/questions/55208188/how-to-fix-appcenter-build-error-netsdk1004 https://intellitect.com/netsdk1004-compile-error/

[adegeo]

@ghogen This was published (and some others): https://docs.microsoft.com/en-us/dotnet/core/tools/sdk-errors/netsdk1005

[ghogen]

@adegeo OK, that's for NETSDK1005 but we are still seeing NETSDK1004 - maybe there's some slight difference if they both deal with a missing assets file.

[ghogen]

@adegeo It looks like @gewarren just added a doc for NETSDK1004. #22517 - Thanks!

If no one is working on NETSDK1045, I could submit one based on the StackOverflow information, as a start.