4 Answers
4

You can specify the properties element in your feature.xml file, which can then be accessd from the feature receiver as indicated by Thomson. But this approach will land you to the problem of compiling your WSP again and again as you change the feature.xml properties.

I would suggest you to maintain any configuration in a SharePoint list. Your feature once activated can then read these values in the code behind. You can use the ConfigStote available on codeplex for maintaining any configurations.

I second storing the config string in the list, or, if you're comfortable with development, what I've done in the past was add a configuration page for my timer job to central admin, and store the connection string for that job in the SPWebApplication.Properties hashtable.

We did things that way because we wanted our settings stored in a place which wasn't easily shown through the UI - you hardly want a list with your database login in plain text. And, actually, adding a page to central admin for that was pretty straight forward.