Shamil Salakhetdinov
shamil at smsconsulting.spb.ru
Mon Dec 7 13:54:55 CST 2009
Hi John -- For solution you can select one of the projects to be used to handle settings. That project is usually a core(utility/generic/settings) class library. Then if you wish you can additionally wrap Properties.Settings.Default... for every/most of the settings into your custom global (Solution scope) properties' wrappers. Such wrapping makes your referencing projects independent on actual implementation of handling of application settings. When that done and works OK you can go and "reinvent the wheel" if needed without any changes in referencing projects... -- Shamil -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Monday, December 07, 2009 5:03 PM To: Discussion concerning Visual Basic and related programming issues. Subject: Re: [dba-VB] Application settings OK, it appears that each project has its own set of properties. If I set the same property in the current project's property set then Properties.Settings.Default["ServerName"].ToString() works just fine. But that is not the behavior I want. I need a SOLUTION property set, which appears to not exist? Which perhaps would explain why those who have done this before roll their own? Does anyone have code to do this so I don't have to roll my own (a.k.a. reinvent the wheel) too? John W. Colby www.ColbyConsulting.com <<< snip >>> __________ Information from ESET NOD32 Antivirus, version of virus signature database 4668 (20091207) __________ The message was checked by ESET NOD32 Antivirus. http://www.esetnod32.ru