Skip to content

Duplicate LINQ articles #16482

Closed
Closed

Activity

  1. Youssef1313 commented on Jan 1, 2020

    @Youssef1313
    Member

    Where they should be consolidated ?

  2. gewarren commented on Jan 4, 2020

    @gewarren
    CollaboratorAuthor

    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.

  3. Youssef1313 commented on Jan 5, 2020

    @Youssef1313
    Member

    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.

  4. mairaw commented on Feb 4, 2020

    @mairaw
    Contributor

    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.

  5. mairaw commented on Feb 4, 2020

    @mairaw
    Contributor

    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.

  6. mairaw commented on Feb 27, 2020

    @mairaw
    Contributor

    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

  7. dotnet-bot commented on Jan 25, 2021

    @dotnet-bot
    Contributor

    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.

  8. added
    won't fixIssues that were closed as part of automated backlog grooming
    on Jan 25, 2021
  9. Youssef1313 commented on Jan 25, 2021

    @Youssef1313
    Member

    @BillWagner This is still an issue. Consider re-opening to track merging the duplicate articles.

  10. removed
    won't fixIssues that were closed as part of automated backlog grooming
    on Jan 25, 2021
  11. BillWagner commented on Mar 4, 2026

    @BillWagner
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions