application-settings

I have an automated build process that sets up the application for a specified mode (e.g. Dev, uat, live). Depending on this mode I want to update Connection Strings to the relevant one. However, in my Data Access Layer there is an app.config file which stores the connection string and this is used to feed the Settings.Settings file. In my builder I update the app.config's xml with the new Connection String and then the solution is built, however the Settings.setting file doesn't get regenerated with the updated app.config connection string and so the app doesn't connect to the correct DB. Is

I am using VS2010 C#.NET 3.5 and application settings (the Settings.settings file). What I want to do is have different settings for my development and production environments without having to litter my code with conditional statements checking for debug mode. What is the common approach to this problem? Or you can just create separate config files and call them: Release.settings Debug.settings then setup conditional build events that copy the appropriate .config file to Settings.Settings if $(ConfigurationName) == Debug xcopy debug.settings settings.settings if $(ConfigurationName) ==

I need a little help with understanding what can I do and cannot in android. I'm working on application which needs to ask user in first start to select a device (internal/external storage) where to save the data which my application is downloading over internet. So I'm trying to find answer for a few questions about this issue : Is there any limit for data in internal/external storage in Android for a single application. Can I set the directory of sqlite database which my app is using and If I can, is it a good practice or not. What should I consider when user decide to change the destination

I'd like to know what is the best solution to manipulate application settings in a cross-platform way. In iOS we can change the settings outside the app in the settings screen, but we don't have that in windows phone and android. So, my idea is to create a normal page/screen inside the app that shows all my application settings and have an interface with Save() and Get() methods that I can implement specific per device using DependencyServices. Is this the right way to do it? The Application subclass has a static Properties dictionary which can be used to store data. This can be accessed from

I am using the vue-webpack template and I have created a settings.json file to store environment variables that should be changed when installing the script. My settings.json (just store the absolute path to the API server): { "apiURL": "//localhost/app/server/API" } How can I keep the file from being minified/bundled in the production version such that I can change it and the updated file will be used next time the app is accessed (without having to build it again) ? In my app I use this file via require : const SETTINGS = require('../settings.json'); I understand that by require ing it