Hi Naomi,

>What is better and why, the way I currently have it in util.cs or the way you showed?

Depends... A static property can make code slightly slower if you also have a static constructor and access it from an instance method. Static properties are also considered risks in stateless classes such as when writing code for the SQL Server CLR. On the other hand it saves memory since there's only one property. Without string interning there's also only one instance of the string. In a static class, though, you have to use a static property.