The name ConfigurationManager does not exist in the current context

Question

I am trying to access connectionStrings from the config file  The code is ASP NET   C   I have added System Configuration to reference and also mentioned with using  But still it wouldn t accept the assembly   I am using VSTS 2008  Any idea what could be the reason    Another weird thing is the assembly name shown as  System configuration   a lower case c which is not how names are displayed for other System assemblies   using System  using System Collections Generic  using System Linq  using System Text  using System Configuration   namespace Utility       public class CommonVariables               public static String ConnectionString                       get   return ConfigurationManager ConnectionStrings  EmployeeEntities   ConnectionString                            Config    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt     lt connectionStrings gt       lt add name  qbankEntities  connectionString  metadata res     qbankModel csdl res     qbankModel ssdl res     qbankModel msl provider System Data SqlClient provider connection string  amp quot Data Source localhost Initial Catalog qbank Persist Security Info True User ID    Password      MultipleActiveResultSets True amp quot   providerName  System Data EntityClient    gt     lt  connectionStrings gt   lt  configuration gt

User · Answer

You may also get this error if you add a reference to a different  unrelated project by mistake   Check if that applies to you

User · Answer

Add the configuration manager file to connect to the database web config

User · Answer

For a sanity check  try creating a new Web Application Project  open the code behind for the Default aspx page  Add a line in Page Load to access your connection string   It should have System Configuration added as reference by default  You should also see the using statement at the top of your code file already   My code behind file now looks like this and compiles with no problems   using System  using System Collections  using System Configuration  using System Data  using System Linq  using System Web  using System Web Security  using System Web UI  using System Web UI HtmlControls  using System Web UI WebControls  using System Web UI WebControls WebParts  using System Xml Linq   namespace WebApplication1     public partial class  Default   System Web UI Page         protected void Page Load object sender  EventArgs e              string connString   ConfigurationManager ConnectionStrings  MyConnectionStringName   ConnectionString                This assumes I have a connection string in my web config with a name equal to  MyConnectionStringName  like so      lt  xml version  1 0  encoding  utf-8    gt   lt configuration gt       lt configSections gt       lt  configSections gt       lt connectionStrings gt           lt add name  MyConnectionStringName              connectionString  Data Source   Initial Catalog MyDatabase Integrated Security True              providerName  System Data SqlClient    gt       lt  connectionStrings gt   lt  configuration gt    Yeah  it s elementary I know  But if you don t have any better ideas sometimes it helps to check against something really simple that you know should work

User · Answer

The configuration manager of web configuration  web config  is obsolete  So see this https   docs microsoft com en-us dotnet api system configuration configurationmanager appsettings redirectedfrom MSDN amp view dotnet-plat-ext-3 1 System Configuration ConfigurationManager AppSettings create a instance of settings var appSettings   ConfigurationManager AppSettings

User · Answer

To Solve this problem go to Solution Explorer And right click reference and click add reference and chose  net and find system configuration select an click ok

User · Answer

If you re getting a lot of warnings  in my case 64 in a solution   like     CS0618   ConfigurationSettings AppSettings  is obsolete   This method is obsolete  it has been replaced by System Configuration System Configuration ConfigurationManager AppSettings    because you re upgrading an older project you can save a lot of time as follows    Add System Configuration as a reference to your References section  Add the following two using statements to the top of each class   cs  file   using System Configuration    using ConfigurationSettings   System Configuration ConfigurationManager    By this change all occurances of   ConfigurationSettings AppSettings  mySetting     will now reference the right configuration manager  no longer the deprecated one  and all the CS0618 warnings will go away immediately   Of course  keep in mind that this is a quick hack  On the long term  you should consider refactoring the code

User · Answer

Adding this answer  as none of the suggested solutions works for me          Right-click on references tab to add reference    Click on Assemblies tab   Search for  System Configuration     Click OK

User · Answer

It s not only necessary to use the namespace System Configuration  You have also to add the reference to the assembly System Configuration dll   by   Right-click on the References   Dependencies Choose Add Reference  Find and add System Configuration     This will work for sure  Also for the NameValueCollection you have to write   using System Collections Specialized

User · Answer

Just install  Install-Package System Configuration ConfigurationManager -Version 4 5 0   then use  using System Configuration

User · Answer

Adding the System Configuration as reference to all the projects will solve this    Go to Project -  Add Reference In the box that appears  click the All assemblies list tab in the left hand list  In the central list  scroll to System Configuration and make sure the box is checked  Click ok to apply  and you ll now be able to access the ConfigurationManager class

User · Answer

Ok   it worked after restarting the VSTS  The link suggested the solution for the same problem  Wish i could have seen it before

User · Answer

Are you sure you have added a reference to the  NET assembly and not something else  I d remove your reference and then try re-adding it  making sure you select from the  NET tab in Visual Studio reference dialogue - the latest version should be 2 0 0 0 in GAC

User · Answer

In NetCore 3 1 I had to use Microsoft Extensions Configuration instead       public static async Task Main string   args                var configuration   new ConfigurationBuilder                SetBasePath Directory GetCurrentDirectory                 AddJsonFile path   appsettings json   optional  false  reloadOnChange  true               Build

User · Answer

If this code is on a separate project  like a library project  Don t forgeet to add reference to system configuration

User · Answer

Right-click on Project Select Manager NuGet Package Find System Configuration Select System Configuration ConfigurationManager by Microsoft Install   now you can   using System Configuration

User · Answer

I have gotten a better solution for the issue configurationmanager does not exist in the current context    To a read connection string from web config we need to use ConfigurationManager class and its method  If you want to use you need to add namespace using System Configuration   Though you used this namespace  when you try to use the ConfigurationManager class then the system shows an error    configurationmanager does not exist in the current context     To solve this Problem   ConfigurationManager ConnectionStrings  ConnectionSql   ConnectionString

User · Answer

In your project  right-click  Add Reference     in the  NET tab  find the System Configuration component name and click OK   using System Configuration tells the compiler IntelliSense to search in that namespace for any classes you use  Otherwise  you would have to use the full name  System Configuration ConfigurationManager  every time  But if you don t add the reference  that namespace class will not be found anywhere   Note that a DLL can have any namespace  so the file System Configuration dll could  in theory  have the namespace Some Random Name  For clarity consistency they re usually the same  but there are exceptions

[c#] The name 'ConfigurationManager' does not exist in the current context

Examples related to c#

Examples related to .net

Examples related to visual-studio

Examples related to visual-studio-2008