As stated in this answer , this should be good if you are not actually modifying any existing behavior (and, more specifically, depending on how that behavior changes). If all the new class does is add new (separate) methods / properties, then you should be fine. However, as is usually the case, it depends. Consider the following issues:
- Who uses your assembly (outsiders or only those who are part of your organization)?
- Can you recompile customers?
- Can you run automatic or manual unit tests for these clients?
- Do you want to add or change the functionality of your LegacyClass?
source share