Hi there, I'm not sure whether this is a valid point to raise and/or whether I should provide some form of an "answer" when providing feedback, though I would like to bring it under the attention of the person/persons responsible for keeping the .Net docs up to date. As provided below by the "Submit feedback" section at the bottom of the page, there was no information provided for the error CS1961 with message "Invalid variance: The type parameter 'T' must be invariantly valid on 'ICollection'. 'T' is covariant." (image below).
Now while the page does suggest to use Google search, MSDN, and SO, I always find it more appropriate to read up on errors, types, and members directly from the provider of a library, package, or framework. This being said, it is not just preference that I'd like to find the relevant information on a provider's page, I also find it quite frustrating when an application provides a hyperlink to a resource while that resource does not exist.
If I may be so bold, my suggestion is to either make Visual Studio not provide a hyperlink to a resource while that resource does not exist, or to populate the appropriate information for all error codes in the UI that specify a hyperlink. While this suggestion does seem demanding, I am willing to assist with creating such documentation where needed when I have time available, I just need to know where and/or how to provide such documentation.
Regards,
NightPr0wl3r
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: bbb051ee-f020-66ba-c601-4a08ad32ef61
Version Independent ID: 58a19505-ac46-c5c8-12cc-fe87b6aa18a7
Hi there, I'm not sure whether this is a valid point to raise and/or whether I should provide some form of an "answer" when providing feedback, though I would like to bring it under the attention of the person/persons responsible for keeping the .Net docs up to date. As provided below by the "Submit feedback" section at the bottom of the page, there was no information provided for the error CS1961 with message "Invalid variance: The type parameter 'T' must be invariantly valid on 'ICollection'. 'T' is covariant." (image below).
Now while the page does suggest to use Google search, MSDN, and SO, I always find it more appropriate to read up on errors, types, and members directly from the provider of a library, package, or framework. This being said, it is not just preference that I'd like to find the relevant information on a provider's page, I also find it quite frustrating when an application provides a hyperlink to a resource while that resource does not exist.
If I may be so bold, my suggestion is to either make Visual Studio not provide a hyperlink to a resource while that resource does not exist, or to populate the appropriate information for all error codes in the UI that specify a hyperlink. While this suggestion does seem demanding, I am willing to assist with creating such documentation where needed when I have time available, I just need to know where and/or how to provide such documentation.
Regards, NightPr0wl3r
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.