- #By default where does atlasti keep user data code#
- #By default where does atlasti keep user data windows#
Which explains why settings were resetting on every compile. Whereas all of my other applications had a hard-coded version like: Build Numbers by using the '*' as shown below: You can specify all the values or you can use the default the Revision and The assembly version has following format : So I checked assemblyinfo.cs, and found this: I noticed it had a seperate directory for every single build of my application, which was strage because none of my other visual studio apps were like this.
#By default where does atlasti keep user data windows#
This was incorrect, it's literally just 'nfig' not '' or having anything to do with your windows login (since it's stored in the profile directory I guess they avoid the redudancy of using the username twice). I was searching for 'nfig' where user was the username of the person currently logged in. I had already tried searching 'documents and settings' folder for nfig, but it came up blank which was adding to the whole confusion. Thanks! the path reference was the most helpful. For example, here is how you can get the local nfig file path:Ĭonfiguration config = ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.PerUserRoamingAndLocal) Ĭonsole.WriteLine("Local user config path: ", config.FilePath) If you want to get to the path programmatically, you can do it using the Configuration Management API (you need to add a reference to ). This is required to isolate different versions of the app deployed side by side. typically the version specified in the AssemblyVersionAttribute. and - information derived from the app domain evidence to provide proper app domain and assembly isolation. is typically the string specified by the AssemblyProductAttribute (same caveats as for company name). is typically the string specified by the Assembl圜ompanyAttribute (with the caveat that the string is escaped and truncated as necessary, and if not specified on the assembly, we have a fallback procedure). To store a setting in the roaming nfig file, you need to mark the setting with the SettingsManageabilityAttribute with SettingsManageability set to Roaming. Settings are stored by default in the local nfig file. is either the roaming profile directory or the local one. The exact path of the nfig files looks something like this: just want to know _where_ it's actually persisting to. This application has a list of rules/filters that is fairly long and tedious to reenter, so it's becoming quite a pain to reinput.Īny ideas? like I said, the persistance feature works great. I would like to be able to export or save the file/registry section where this is stored, recompile my app, and then reimport the settings. and I have to reinput them through the application. everytime I recompile it, it loses it's saved settings.
#By default where does atlasti keep user data code#
My reason for asking, is that I have an application that I frequently recompile and push code updates to. I poked around in the registry and googled for this, but I can't figure out where it's saving this to. where does this actually get persisted to? I thought it was the nfig file, but when I check this file it always contains the default values. Hey, I have an application that saves it's settings in the "settings" tab of the program properties page in VS2005.
0 kommentar(er)
