this post was submitted on 21 Jun 2023
9 points (100.0% liked)
.NET
1484 readers
5 users here now
Getting started
Useful resources
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
Wikipedia pages
- .NET (open source & cross platform)
- .NET Framework (proprietary & Windows-only)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
More of a VS thing but the fact that you need to have copilot to have a good intellisense experience.
Let's say you are defining several
JsonPropertyName
attributes for your properties, while writing:Base intellisense will propose something completely unrelated for the property while with the github copilot extension, it will automatically recommend the correct property
PostId
after writing theJsonPropertyName
attribute.Same thing if you are defining Validators in the same file as the validated object:
With the copilot extension, after 2 or 3 files, it will automatically propose a validator class for autofill. Default intellisense? You got to type it out manually for every file.