>>Hi everybody,
>>
>>I was thinking that instead of accessing my connection string through configuration manager in several procedures of our global static class I'll make it a const property. So, based on another existing const I put
>>

>>   private const string TelephoneRegex = @"(1\s*[-\/\.]?)?(\((\d{3})\)|(\d{3}))\s*[-\/\.]?\s*(\d{3})\s*[-\/\.]?\s*(\d{4})\s*(([xX]|[eE][xX][tT]| )\.?\s*(\d+))*";
>>    private const string ConnectionString = System.Configuration.ConfigurationManager.ConnectionStrings["FCCMSConnectionString"].ConnectionString;
>>

>>
>>at the very top of the class.
>>
>>However, I'm getting this error
>>
>>Error 1 'Util.ConnectionString' is of type 'string.' A const of reference type other than string can only be initialized with null
>>
>>Do you know if this is a wrong approach? What can I do to use this as a property?
>>
>
>If you mark something as "const" the compiler has to be able to resolve it at compile time (not runtime). That's why it's not working. You could expose it via a property with a get only - read it into a member on first access. Then it's read-only (if that's really your goal) and you're not having to read from the web.config on each access.

I tried to remove the word const and got a new error Error 1 'Util.ConnectionString': cannot declare instance members in a static class

I guess I would put it back to all places where it was used. Or may be you can give me some code sample?

Thanks again.