Skip to main content

Difference Between Dynamic and Object Keyword in C#

The dynamic keyword and objects don't perform compile-time type checks and identify the type of objects at runtime only and both can store any type of the variable. Objects were introduced in 1.0 C#. Later, why was Dynamic introduced in 4.0 C# when Objects already exist.

Difference 1 :

Object: the Compiler has little information about the type. It's not compiler safe.
You need to do an explicit type casting every time you want to get the value back and forth.

object  a = "Nikhil Sangani";
string a1 = a.ToString();

Dynamic: In a dynamic variable, the compiler doesn't have any information about the type of variable.

dynamic  a = "Nikhil Sangani";
string a1 = a;

Difference 2 :

Object: When using an object, you need to cast the object variable to the original type to use it and do the desired operations. In the first difference, the following example shows an error.

object  a = "Nikhil Sangani";
string a1 = a;

Now you need to do an explicit type casting every time.

Dynamic: Casting is not required but you need to know the properties and methods related to the stored type.

The Object is useful when we don't have more information about the data type. Dynamic is useful when we need to code using reflection or dynamic languages or with the COM objects and when getting a result out of the LINQ queries.
Labels:
Location: Ahmedabad, Gujarat, India

Comments

Post a Comment

Popular posts from this blog

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests: Write tests for all public methods Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early. public class Calculator { public int Add(int a, int b) { return a + b; } } [TestClass] public class CalculatorTests { [TestMethod] public void Add_ShouldReturnCorrectSum() { // Arrange Calculator calculator = new Calculator(); int a = 1; int b = 2; // Act int result = calculator.Add(a, b); // Assert Assert.AreEqual(3, result); } } Test boundary conditions  Make sure to test boundary conditions, such a...
Post a Comment
Read more

What to choose between .NET Core and .NET?

 .NET Framework is a better choice if you: you don't have enough time time to learn new technology. Need a stable environment to work in. Have nearer release schedules. you are already working on an existing app and extending its functionality. If already have an existing team with .NET expertise and building production-ready software. Do not want to deal with continuous upgrades and changes. Building Windows client applications using Windows Forms or WPF .NET Core is a better choice if you: IF you wanted to deploy your app on Windows, Linux, and Mac operating systems. Are not afraid of learning new things. Are not afraid of breaking and fixing things since .NET Core is not fully matured yet. When you are learning .NET. work on open source.
Post a Comment
Read more