I used to have one class for one file. For example car.cs has the class car. But as I program more classes, I would like to add them to the same file. For
You should refrain from doing so, unless you have a good reason.
One file with several small related classes can be more readable than several files. For example, when using 'case classes', to simulate union types, there is a strong relationship between each class. Using the same file for multiple classes has the advantage of grouping them together visually for the reader.
In your case, a car and a door do not seem related at all, and finding the door class in the car.cs file would be unexpected, so don't.