C# read-only calculated properties, should they be methods?
c#, standards
Solution
It's OK to use calculated properties rather than methods, as long as the calculation doesn't take a noticeable time
See Property usage guidelines
Problem
I have several entities that have calculated fields on them such as TotalCost. Right now I have them all as properties but I'm wondering if they should actually be methods. Is there a C# standard for this? ``` public class WorkOrder { public int LaborHours { get; set; } public decimal LaborRate { get; set; } // Should this be LaborCost()? public decimal LaborCost { get { return LaborHours * LaborRate; } } } ```