this post was submitted on 21 Jun 2023
28 points (93.8% liked)

.NET

1503 readers
3 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 2 years ago
MODERATORS
28
submitted 2 years ago* (last edited 2 years ago) by sisyphean to c/dotnet
 

The original thread is on the devil’s website and I don’t want to direct traffic to it, so here’s a link to the tweet instead:

https://twitter.com/davidfowl/status/1671351948640129024?s=46&t=OEG0fcSTxko2ppiL47BW1Q

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 2 years ago* (last edited 2 years ago)

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:

[JsonPropertyName("postId")]
public int PostId { get; set; }

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 the JsonPropertyName attribute.

Same thing if you are defining Validators in the same file as the validated object:

// Post.cs

public class Post ...

public class PostValidator: AbstractValidator<Post> ...
}

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.