The latest version of C# allows you to define the body of the interface method.
For example, consider you have a project of Asset Management which has an interface, IAsset, that has properties AssetName, AssetAge, Id and so on.
- using System;
- using System.Collections.Generic;
- using System.Linq;
- using System.Text;
- using System.Threading.Tasks;
-
- namespace Stucts.New_Features.Interface
- {
- interfaceIAsset
- {
- string AssetName { get; set; }
- string AssetAge { get; set; }
- string Id { get; set; }
-
- }
- }
Now, consider you have this interface inherited in multiple classes, like FixedAssets, TemporaryAssets, and so on.
- using System;
- using Stucts.New_Features.Interface;
-
- namespace Stucts.New_Features
- {
- class FixedAsset : IAsset
- {
- public string AssetName { get; set ; }
- public string AssetAge { get; set; }
- public string Id { get; set; }
- }
- }
Consider you want to add this new feature to your application which moves the asset to archive after certain years as per customer needs. It may be possible that you need to implement this logic for all kinds of assets or just for a few or some different logic based on other calculations.
In the older version of C#, you need to define a non-body method in the interface and implement that method in all the other classes. In some cases, this might not seem a very big issue but I know when you are working on ultra-large-scale software, then this is a headache no one wants.
In C# 8.0, you can define the default implementation of a method in interface and classes can use that method or if you can give a different definition to the same method in child classes.
- public void MoveAssetToArchive(int age)
- {
-
- }
You can start using this method in all the child classes without implementing it.
- FixedAsset _fixAsset = newFixedAsset() {
- AssetAge="4",
- AssetName="HTC Explorer Mobile phone",
- Id = "1001"
- };
- IAsset _IAsset = _fixAsset;
- _IAsset.MoveAssetToArchive(4);
Notice the following section of the test.
- IAsset _IAsset = _fixAsset;
- _IAsset.MoveAssetToArchive(4);
Well, that saved a lot of time and efforts :)
Similarly, you can also declare a variable as well as static members in the interface.
I would love it if you guys create a demo project with a scenario where we might need to declare static members and behaviors in an interface. Please do try. I will create a demo with a scenario and write it in the blog soon so that we can discuss it. Comment if you have any question or want to discuss something.
Meanwhile, follow and subscribe to the blog to get notifications of it.
Ravi GuptaPosted Oct 12, 2022, 12:20 PM
Is this not changing the concept we learnt about an interface? What would be the difference between a abstract class and an interface in c#?
bank minePosted Oct 10, 2019, 11:28 AM
So if the method in the interface has to be updated in the child class? do we use the same signature of the method in interface with a new implementation? or what about when there is a partial change in only one of the child classes?