When We should use record type instead of Class in c#?

Question

As I know record type can be immutable(cannot be changed once object is created) reference type.

So what are different prectical scenarios where record type uses is more relevant and appropriate instead of Class?

Rajanikant Hawaldar · Answer

If main purpose of storing data then use record types, if responsibility need to define then use class

Aravind Govindaraj · Answer

Hi, Please refer to this link it clears your queries https://josipmisko.com/posts/c-sharp-class-vs-record

Munib Butt · Answer

Use Records in C# when you want to compare instances using values of the properties.

Muhammad Imran Ansari · Answer

In a simple way, a class is an OOP concept that wraps data with functionality, while a record represents a set of data. Records should not have any state changes after instantiation (immutable state), while classes change properties. Use a record when an object's only purpose is to contain public data. On other hand, use a class if your object has unique logic. Classes are mutable so even if they have the same data, doesn't mean they are the same.

Saravanan Ganesan · Answer

Record types are ideal for representing immutable data with value semantics, such as entities with no identity change, like date/time objects, configurations, or DTOs. They simplify code, enhance readability, and reduce the chance of bugs in scenarios where data changes should not occur, making them more appropriate than classes for such cases.