application-settings

I have recently became familiar with C# application settings, and it seems cool. I was searching for a way to store a list of custom objects, but I couldn't find a way! Actually I saw a post to store int[] , but it wasn't helpful for this problem. I tried to change the config of that solution in order to make it suitable for my problem. the XML config file of that was: <Setting Name="SomeTestSetting" Type="System.Int32[]" Scope="User"> <Value Profile="(Default)" /> </Setting> I tried to address my object as quoted below in the type attribute but it wasn't helpful since it doesn't recognizing

Given a "standard" spring boot application with a @RestController , eg @RestController @RequestMapping(value = "foo", produces = "application/json;charset=UTF-8") public class MyController { @RequestMapping(value = "bar") public ResponseEntity<String> bar( return new ResponseEntity<>("Hello world", HttpStatus.OK); } } Is there an annotation or technique that prevents the endpoint from starting at all if/unless a certain application property exists/doesn't exist. Note: Testing a property inside the method and exploding is not a solution, because the endpoint will exist. I don't care about the

I have an application that I am just migrating to Azure. Currently I use web.config transformation to manage changing the database connecting string dev/staging/prod environments. How is it best to manage these multiple connection strings in Azure? Jonathan McIntire In cases where it doesn't matter if the developer can see production credentials, you can use the built-in Visual Studio 10 config transformations. If this is what you're looking for, follow these steps: 1.Navigate to your Azure project folder in file explorer 2. Make a copy of ServiceConfiguration.cscfg 3. Rename copy to

In large and complex software products managing configurable settings becomes a major pain. Two approaches I've seen to the problem are: have each component in the system load its own configuration from config files or registry settings. have a settings loader class that loads all the configurable system settings and have each component query the settings loader for its settings. These approaches both feel wrong to me. Are there any design patterns that could be used to simplify the problem? Maybe something that would take advantage of the dependency injection technique. I prefer to create an

I would like to include the application version and internal revision, something like 1.0.1 (r1243), in my application's settings bundle. The Root.plist file contains a fragment like this... <dict> <key>Type</key> <string>PSTitleValueSpecifier</string> <key>Title</key> <string>Version</string> <key>Key</key> <string>version_preference</string> <key>DefaultValue</key> <string>VersionValue</string> <key>Values</key> <array> <string>VersionValue</string> </array> <key>Titles</key> <array> <string>VersionValue</string> </array> </dict> and I would like to replace the "VersionValue" string at build