I have used a lot of static methods in Data Access Layer (DAL) like:
public static DataTable GetClientNames()
{
return CommonDAL.GetDataTable("....");
}
But I found out that some developers don’t like the idea of static method inside DAL. I just need some reason to use or not use static methods inside DAL.
Thanks
Tony
From purists’ point of view, this violates all kinds of best practices (like, dependency on implementation, tight coupling, opaque dependencies, etc.). I would’ve said this myself, but recently I tend to move towards simpler solutions without diving too much in “enterprizey” features and buzzwords. Therefore, if it’s fine with you do write code like this, if this architecture allows for fast development and is testable and, most important, solves your business problem — its’s just fine.