Hi everyone. We continue with my second article on SQL commands. If you haven’t read my first article, you can find it here: Create and Use a Database with SQL Commands Hey everyone. In this article we are going to learn how to create and use a database with SQL commands. I am going to…taylancanh.medium.com Let’s continue where we left off. We will continue with ready-made functions in this article.

Hey everyone. In this article we are going to learn how to create and use a database with SQL commands. I am going to do this processes with MSSQL. Let’s start. First of all, SQL Server and Management Studio must be installed on your computer. …

When developing a project, there are many ways to manage the project’s database connections and processes. However, many of these methods are new and slower than the old ones. Therefore, these methods should be learned well and the appropriate one should be used. First of all, if newer ones are…

Hey everyone. In this article, I am going to talk about Scoped, Transient and Singleton. Let me first talk about what they are. These are three different lifetime options of the Dependency Injection technique that comes with ASP .NET Core. Now let’s examine each one one by one. Then…

Hey everyone. In this article, I am going to talk about Factory Patterns. Firstly, we know that patterns are created for a problem. So why was the Factory Pattern created? Where do we use it? Here we go.

Hey everybody I’ll explain the Singleton pattern, which is one of the most preferred design patterns in the industry. Singleton design pattern guarantees that only 1 object is created at runtime.

Firstly what are these patterns? These patterns are not algorithm or code blogs. Design patterns are solutions to common problems software developers face during software development. These patterns were found by trial and error after long processes. After that developers gave names to these problems. The design pattern phrase originated…

Hey everybody it is fifth and last principle of SOLID Principles. This principle means that a high-level modules should not depend on low-level modules. Both should depend on abstractions. So abstractions should not depend on details. Details should depend on abstractions. Let’s say you have a customer and he is…

Hey everybody it is fourth principle of SOLID Principles. This principle means that a client should never be forced to implement an interface that it doesn’t use, or clients shouldn’t be forced to depend on methods they do not use. After the classical definition. For example, let’s say you have…