>I describe situation with one assembly. If you have more, you can separate class with static properties in another assembly, which will reference no other assemblies. So all other assemblies will be able to access shared properties.


I ran into this situation a little while ago. Is it a common practice to create a separate assembly just to store the "global" variables? I didn't want to do that. What I did instead was create a CS file and set it on an unique namespace, then I add this CS file to all of my projects. This way I can reference to the static variables and constants stored in this file from everywhere. It does produce warning messages at compile time but it seems to work fine.