You can do something like: int maxRequestLength = 0; HttpRuntimeSection section = ConfigurationManager.GetSection(“system.web/httpRuntime”) as HttpRuntimeSection; if (section != null) maxRequestLength = section.MaxRequestLength;
Yes, you can. You need to be sure that any configuration you are referencing in your tests actually exist in the app.config of the test project. In other words, the project where your test is in, does not have a connection string “FertigungRead” defined in its app.config. One way to do this is to add … Read more
ConfigurationManager is a part of the System.Configuration after .Net 2.0. Add a reference to the System.Configuration dll. Try using System.Configuration.ConfigurationManager.
Make sure you have a reference to the assembly System.Configuration.dll
I can’t remember where I found this solution but here is how I managed to load a specific exe configuration file: ExeConfigurationFileMap map = new ExeConfigurationFileMap { ExeConfigFilename = “EXECONFIG_PATH” }; Configuration config = ConfigurationManager.OpenMappedExeConfiguration(map, ConfigurationUserLevel.None);
A quick test seems to show that these settings are only loaded at application startup. //edit the config file now. Console.ReadLine(); Console.WriteLine(ConfigurationManager.AppSettings[“ApplicationName”].ToString()); Console.WriteLine(“Press enter to redisplay”); //edit the config file again now. Console.ReadLine(); Console.WriteLine(ConfigurationManager.AppSettings[“ApplicationName”].ToString()); Console.ReadLine(); You’ll see that all outputs remain the same.
Although the using System.Configuration; command is automatically generated in the using section, for some reason the actual reference is not set. Go into add reference, .Net tab, and choose System.Configuration. ConfigurationManager will now be resolved. If you go to the project where the exact same setup works just fine and look at the references, you … Read more
http://mostlytech.blogspot.com/2007/11/programmatically-enumerate-wcf.html // Automagically find all client endpoints defined in app.config ClientSection clientSection = ConfigurationManager.GetSection(“system.serviceModel/client”) as ClientSection; ChannelEndpointElementCollection endpointCollection = clientSection.ElementInformation.Properties[string.Empty].Value as ChannelEndpointElementCollection; List<string> endpointNames = new List<string>(); foreach (ChannelEndpointElement endpointElement in endpointCollection) { endpointNames.Add(endpointElement.Name); } // use endpointNames somehow … Appears to work well.
Suffered from exact issue. Problem was because of NameValueSectionHandler in .config file. You should use AppSettingsSection instead: <configuration> <configSections> <section name=”DEV” type=”System.Configuration.AppSettingsSection” /> <section name=”TEST” type=”System.Configuration.AppSettingsSection” /> </configSections> <TEST> <add key=”key” value=”value1″ /> </TEST> <DEV> <add key=”key” value=”value2″ /> </DEV> </configuration> then in C# code: AppSettingsSection section = (AppSettingsSection)ConfigurationManager.GetSection(“TEST”); btw NameValueSectionHandler is not supported any … Read more
You need to reference System.Configuration.dll in your project as well as the “using” statement. Namespaces are (sometimes) “split” across assemblies. That means that types in a single namespace are actually in different assemblies. To determine which assembly a BCL or FCL type is in, look it up on MSDN. If you look at the help … Read more