You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's probably fine to have a LINQ section in each language's TOC, but for articles that are duplicated, we could either convert them to an include file that's reused in each TOC, or we could choose one location (I'd say C#) and then link to that file from the other (VB) TOC - link it with a contextual TOC link so you don't jump to the C# TOC when you click it.
Wouldn't it be better to find some directory that holds LINQ article for both languages ?
I was thinking of having a linq directory in docs\standard and move the articles in both languages there. For articles that are in only one language, It might be easy to write the snippets in the other language. So, at the end, the linq folders in csharp or visualbasic will be completely removed, and redirected to the new linq folder in standard. Currently, there is one article related to linq in docs\standard folder, it may be moved to that linq folder after creating it.
I've opened #16969 so you can see what we're doing there and comment on the direction if wanted. But we're basically doing exactly what @Youssef1313 mentioned. Including the move of the standalone LINQ article from standard to standard\linq.
But that section is large, so it might take a while to finish and merge.
This issue has been closed as part of the issue backlog grooming process outlined in #22351.
That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.
Closing as the strategy around these articles has changed.
Effectively, the VB docs won't be updated. Like the product, we're setting stability as the primary goal. The C# docs will (and have) evolved as C# has evolved.
Activity
Youssef1313 commentedon Jan 1, 2020
Where they should be consolidated ?
gewarren commentedon Jan 4, 2020
It's probably fine to have a LINQ section in each language's TOC, but for articles that are duplicated, we could either convert them to an include file that's reused in each TOC, or we could choose one location (I'd say C#) and then link to that file from the other (VB) TOC - link it with a contextual TOC link so you don't jump to the C# TOC when you click it.
Youssef1313 commentedon Jan 5, 2020
Wouldn't it be better to find some directory that holds LINQ article for both languages ?
I was thinking of having a linq directory in
docs\standardand move the articles in both languages there. For articles that are in only one language, It might be easy to write the snippets in the other language. So, at the end, the linq folders in csharp or visualbasic will be completely removed, and redirected to the new linq folder in standard. Currently, there is one article related to linq in docs\standard folder, it may be moved to that linq folder after creating it.mairaw commentedon Feb 4, 2020
This is similar to the issue #4728. The vendor team has started the consolidation of the LINQ to XML articles under standard/linq. You can see the progress here: https://github.com/dotnet/docs/tree/linq-to-xml
Next step was going to be to move into the other sections.
mairaw commentedon Feb 4, 2020
I've opened #16969 so you can see what we're doing there and comment on the direction if wanted. But we're basically doing exactly what @Youssef1313 mentioned. Including the move of the standalone LINQ article from standard to standard\linq.
But that section is large, so it might take a while to finish and merge.
mairaw commentedon Feb 27, 2020
Just found out that there dupe articles in other areas too. For example: https://docs.microsoft.com/en-us/previous-versions/hh534540(v=vs.140) has the links to the C# and VB version
dotnet-bot commentedon Jan 25, 2021
This issue has been closed as part of the issue backlog grooming process outlined in #22351.
That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the
@dotnet/docsteam for visibility.Youssef1313 commentedon Jan 25, 2021
@BillWagner This is still an issue. Consider re-opening to track merging the duplicate articles.
BillWagner commentedon Mar 4, 2026
Closing as the strategy around these articles has changed.
Effectively, the VB docs won't be updated. Like the product, we're setting stability as the primary goal. The C# docs will (and have) evolved as C# has evolved.