I have a couple of entities which will pretty much never change (i.e. a list of Countries, Regions etc.) And it got me thinking... would a static repository make sense for these entities in addition to the normal repositories? I say in addition, because these entities will still interact with other entities, and I still want them under a single Unit of Work so they share the same context.
However, I'm sure there is a better way to go about it. I'm new to ASP.NET and the .NET Framework, but is there a way to define application wide data that will be used throughout the life of the program? Is that the best way to go about it?
Or is it better to just define a static class with collections of these entities and I can just grab these from there when I need it?