Empty constructor or no constructor

Question

I think it is not mandatory to have a default constructor in a class (C#).

So, in that situation shall I have an empty constructor in the class or can I skip it?

Is it a best practice to have an empty default constructor?

Class test {    public test()    {     }         ...... } 

or

Class test {         ...... } 

Answer 1

If the class won't be used by third parties and you don't need an overloaded constructor, don't write an empty constructor.

But...

Imagine you already shipped the product, and third parties use your class. A few months later there's a new requirement that makes you add a constructor with an argument.

Now, by doing so, the C# compiler no longer generates a default constructor. If you don't add an empty constructor explicitly, the third party code will be break.

In my opinion, you should always define empty constructors (one liner) for public classes used by third parties.