Skip to content

[Everyday C#] Add a tuples & types tutorial #45114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
BillWagner opened this issue Mar 4, 2025 · 0 comments · Fixed by #45622
Closed

[Everyday C#] Add a tuples & types tutorial #45114

BillWagner opened this issue Mar 4, 2025 · 0 comments · Fixed by #45622
Assignees
@BillWagner
Labels
dotnet-csharp/svc get-started/subsvc 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer

Comments

@BillWagner
Copy link
Member

BillWagner commented Mar 4, 2025 •
edited by sequestor bot
Loading

Type of issue

Missing information

Description

This section should have a basic tutorial to use and create data types. This should stop before inheritance, interfaces, or even making the distinction between classes and structs. Tuples and records might be the only types covered here.

Page URL

https://learn.microsoft.com/en-us/dotnet/csharp/tour-of-csharp/tutorials/

Content source URL

https://github.com/dotnet/docs/blob/main/docs/csharp/tour-of-csharp/tutorials/index.md

Document Version Independent Id

287733f4-7593-ba5e-f26c-531fde328319

Article author

@BillWagner

Metadata

  • ID: b8cdfbba-c2bd-f9b0-52a9-d82cc9b2dcf9
  • PlatformId: e2683e45-7f8b-d840-6078-3bfeb7f3f434
  • Service: dotnet-csharp
  • Sub-service: get-started

Related Issues

Associated WorkItem - 402712
@BillWagner BillWagner self-assigned this Mar 4, 2025
@github-project-automation github-project-automation bot moved this to 🆕 New in Everyday C# Mar 4, 2025
@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Mar 4, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@BillWagner BillWagner added 🗺️ reQUEST Triggers an issue to be imported into Quest. 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. and removed ⌚ Not Triaged Not triaged labels Mar 4, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 4, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Mar 5, 2025
@BillWagner BillWagner moved this from 🔖 Ready to 🏗 In progress in dotnet/docs March 2025 sprint project Mar 20, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 20, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Mar 20, 2025
@BillWagner BillWagner moved this from 🏗 In progress to Slipped in dotnet/docs March 2025 sprint project Apr 2, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@BillWagner BillWagner moved this from 🔖 Ready to 🏗 In progress in dotnet/docs April 2025 sprint project Apr 2, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 2, 2025
@BillWagner BillWagner moved this from 🏗 In progress to 👀 In review in dotnet/docs April 2025 sprint project Apr 3, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 3, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 3, 2025
@BillWagner BillWagner mentioned this issue Apr 3, 2025
Merged
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Everyday C# Apr 8, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/docs April 2025 sprint project Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BillWagner BillWagner

Labels
dotnet-csharp/svc get-started/subsvc 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer
Projects
Everyday C#
Status: ✅ Done
dotnet/docs April 2025 sprint project
Status: ✅ Done
dotnet/docs March 2025 sprint project
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Get Started tutorial on types BillWagner/docs
1 participant
@BillWagner