#post

.NET 6 is on the way, and I wanted to share some of my favorite new APIs in .NET and ASP.NET Core that you are going to love. Why are you going to love them? Well because they were directly driven by our fantastic .NET developer community! Let’s get started!

Read more...

#post

For .NET 6, we have made FileStream much faster and more reliable, thanks to an almost entire re-write. For same cases, the async implementation is now a few times faster!

Read more...

#post

In this post, I'd like to have a look into minimal APIs.

With the preview 4, Microsoft simplified the simplest project template to an absolute minimum. Microsoft created this template to make it easier for new developers to start creating small microservices and HTTP APIs.

Read more...

#post

Now, for the final post in this mini-series, let's turn our attention to a feature that was originally scheduled for release in C# 10, but didn't quite make the cut: required properties.

Read more...

📝 What is the difference between continue and break statements in C#?

🔸 using break statement, you can jump out of a loop

🔸 using continue statement, you can jump over one iteration and then resume your loop execution

#post

📝 When to use Finalize vs Dispose?

🔸 The finalizer method is called when your object is garbage collected and you have no guarantee when this will happen (you can force it, but it will hurt performance).

🔸 The Dispose method, on the other hand, is meant to be called by the code that created your class so that you can clean up and release any resources you have acquired (unmanaged data, database connections, file handles, etc) the moment the code is done with your object.

The standard practice is to implement IDisposable and Dispose so that you can use your object in a using statement such as using(var foo = new MyObject()) { }.

And in your finalizer, you call Dispose, just in case the calling code forgot to dispose of you.

#post

📝 What are Property Accessors?

The get and set portions or blocks of a property are called accessors.

These are useful to restrict the accessibility of a property.

🔸 The set accessor specifies that we can assign a value to a private field in a property and without the set accessor property it is like a read-only field.

🔸 By the get accessor we can access the value of the private field. A Get accessor specifies that we can access the value of a field publicly.

#post

📝 You have defined a destructor but it never executed. Why?

The runtime environment automatically invokes the destructor of a class to release the resources that are occupied by variables and methods of an object.

However, in C#, programmers cannot control the timing for invoking destructors, as Garbage Collector is only responsible for releasing the resources used by an object.

Garbage Collector automatically gets information about unreferenced objects from .NET's runtime environment and then invokes the Finalize() method.

Although, it is not preferable to force Garbage Collector to perform garbage collection and retrieve all inaccessible memory (programmers can use the Collect() method of the Garbage Collector class to forcefully execute Garbage Collector).

Take notice that the destructor doesn't (and can't) have a public modifier in-front of it, it's sort of an hint that you can't explicitly call the destructor of an object.

#post

📝 What is the difference between a Struct and a Class in C#?

Class and struct both are the user defined data type but have some major difference:

Struct

🔸 The struct is value type in C# and it inherits from System.Value Type.

🔸 Struct is usually used for smaller amounts of data.

🔸 Struct can't be inherited to other type.

🔸 A structure can't be abstract.

Class

🔸 The class is reference type in C# and it inherits from the System.Object Type.

🔸 Classes are usually used for large amounts of data.

🔸 Classes can be inherited to other class.

🔸 A class can be abstract type.

🔸 We can create a default constructor.

#post

All of these interfaces inherit from IEnumerable. That interface basically lets you use the class in a foreach statement (in C#).

🔸 ICollection is the most basic of the interfaces you listed. It's an enumerable interface that supports a Count and that's about it.

🔸 IList is everything that ICollection is, but it also supports adding and removing items, retrieving items by index, etc. It's the most commonly-used interface for "lists of objects".

🔸 IQueryable is an enumerable interface that supports LINQ. You can always create an IQueryable from an IList and use LINQ to Objects, but you also find IQueryable used for deferred execution of SQL statements in LINQ to SQL and LINQ to Entities.

🔸 IDictionary is a different animal in the sense that it is a mapping of unique keys to values. It is also enumerable in that you can enumerate the key/value pairs, but otherwise it serves a different purpose than the others you listed.

#post

📝 What is an Abstract Class?

The abstract modifier indicates that the thing being modified has a missing or incomplete implementation. The abstract modifier can be used with classes, methods, properties, indexers, and events.

An Abstract class is a class which is denoted by abstract keyword and can be used only as a Base class.

Abstract classes have the following features:

🔸 An abstract class cannot be instantiated.

🔸 An abstract class may contain abstract methods and accessors.

🔸 It is not possible to modify an abstract class with the sealed modifier because the two modifiers have opposite meanings. The sealed modifier prevents a class from being inherited and the abstract modifier requires a class to be inherited.

🔸 A non-abstract class derived from an abstract class must include actual implementations of all inherited abstract methods and accessors.

#post

📝 How to implement the Where method in C#?

The yield keyword actually does quite a lot here. It creates a state machine "under the covers" that remembers where you were on each additional cycle of the function and picks up from there.

The function returns an object that implements the IEnumerable<T> interface. If a calling function starts foreaching over this object, the function is called again until it "yields" result based on some predicate.

This is syntactic sugar introduced in C# 2.0. In earlier versions you had to create your own IEnumerable and IEnumerator objects to do stuff like this.

#post

📝 What is namespace in C#?

A namespace is designed for providing a way to keep one set of names separate from another. The class names declared in one namespace does not conflict with the same class names declared in another.

🔸 NET uses namespaces to organize its many classes.

🔸 Declaring your own namespaces can help you control the scope of class and method names in larger programming projects.

 SampleNamespace
{
    class SampleClass
    {
        public void SampleMethod()
        {
            System.Console.WriteLine(
              "SampleMethod inside SampleNamespace");
        }
    }
}

#post