Skip to main content

System.Configuration in .Net Framework 2 onwards - part 2

Some people asked why do you have to explicitly add  reference to System.Configuration.dll assembly? Why can't Visual Studio work out latest version based on the Target framework? Also why is this still the case in .Net Framwork 4.0?


here is the secret.....


In .Net 1.1, System.Configuration namespace was included in System.dll assembly. So they had to keep this namespace in all future release of .Net framework to make it backward compatible.

From .Net 2.0 onwards, Microsoft created a new assembly System.Configuration.dll which includes the namespace System.Configuration. This namespace includes all new functionality.

When you create a new project in Visual Studio (any version), by default it adds reference to System.dl. Hence when you just reference System.Configuration namespace using "Using or Imports", it references the namespace within System.dll. Hence you get old functionality.

By adding a reference to System.Configuration.dll, now you have System.Configuration namespace available from two assemblies: System.dll and System.Configuration.dll. The compiler resolves the reference to the classes to either assembly depending on which class/method you are using. However as System.Configuration namespace from System.dll is marked as Obsolete (I guess using attributes), you get a compiler warning if you use old functionality. This could one of the reason they have changed ConfigurationSettings to ConfigurationManager so that it resolves to correct namespace. Now you know why!

Mystery solved!

Comments

Post a Comment

Popular posts from this blog

Searching Unicode characters in Oracle table

Oracle implementation of Regular expression has no support for using hexadecimal code to search for Unicode characters. The only way to search for Unicode character is it use the character itself. Normally with Regular expression, you can use \x or \u followed by hexadecimal code to search for any character. E.g. \x20 will match space. But REGEXP_LIKE in Oracle does not support \x. You need to use unistr function to convert the code to equivalent character and then use it with REGEXP_LIKE. E.g. REGEXP_LIKE(source,'[' ||unistr('\0020')|| ']');
Post a Comment
Read more

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0
Post a Comment
Read more

How to get started with .Net Core and Lambda functions?

 Recently I started experimenting with .Net Core and AWS Lambda functions, I thought I will share the steps I took to get started Tools to install .Net Core 3.1 -  https://dotnet.microsoft.com/download/dotnet-core/3.1 AWS CLI -  https://aws.amazon.com/cli/   AWS Account - 12 months Free Tier -  https://aws.amazon.com/free Terminal - on iOS I use iTerm2 -  https://www.iterm2.com   Once you installed the above tools, head to AWS console and login with your root account to create an account which will be used by AWS CLI. Please see steps here   Now you can configure AWS CLI as detailed here . Verify that you able to connect to AWS service using CLI. To make life little easy with dotnet core and Lambda functions, you need to install AWS Extensions nuget pack for .Net CLI dotnet tool install -g Amazon.Lambda.Tools You can also install templates to get started quickly  dotnet new -i Amazon.Lambda.Templates That's it. Now the fun part!!!  Creat...
Post a Comment
Read more