Thoughts on .Net & Coding

IdentityServer is an implementation of OpenID Connect and OAuth2 specifications that ASP.NET Core developers can use to secure their applications and APIs. Beginners often find it bit tricky to setup and configure the applications to use this popular framework. To that end this article series attempts to provide a quick tour of setup and configuration required to put IdentityServer to use. I am not going to explain the basic OAuth2 and OpenID Connect terminology here. A lot of good resources are available on the internet explaining those basics. You can also go through the IdentityServer documentation to familiarize yourself with the framework.

As a C# developer you expose functionality using classes and objects. Many a times the code required to accomplish a task using these classes and objects tends to be complex. In an attempt to reduce this complexity you might want to device a technique that makes your code more readable and natural. That is where Fluent Interface and Method Chaining can be useful. The remainder of this article discusses these techniques with simple examples. My aim is to quickly introduce you to these concepts. So, the examples are kept simple rather than building a full-fledge example.

ASP.NET Core web applications often need to redirect a request to another resource based on some condition. There are multiple ways in which you can accomplish this task in ASP.NET Core MVC and Razor Pages. To that end this article discusses them with examples.

ASP.NET Core Web APIs and controllers often need to serialize JSON data to JavaScript clients. On the server side your C# classes typically use Pascal Casing to name properties whereas JavaScript code often uses Camel Casing for property names. Therefore it would be worthwhile to take a quick look at how ASP.NET Core serializes data in JSON format from Web API and MVC controllers.

In the previous part of this article and video series you learned about various types of decorators. Continuing our learning further this part discusses how generics can be utilized in TypeScript. If you are a C# developer chances are you already know generics. You can use that concept in TypeScript also. To that end this article discusses a few examples that show how to put generics to use in TypeScript classes and methods.

In the previous part of this article and video series you were introduced to TypeScript decorators. You know that decorators come in different flavors such as class, property, method, accessor, and parameter decorators. You also learned to create class decorators. Continuing our learning further this part shows you how to create property and method decorators.

In the previous part of this article and video series you learned about TypeScript inheritance. In this article you will learn about a feature of TypeScript that allows you to annotate and modify classes and class members. This feature is called Decorators. Decorators is an experimental feature and you need to enable them in your TypeScript configuration file. You will find TypeScript decorators analogous to C# attributes in that they form the metadata of a class and class members.

Object oriented programming languages such as C# allow you to inherit functionality from base class. TypeScript also offers inheritance capabilities so that your classes can inherit from other classes. TypeScript doesn't support multiple inheritance (although your class can implement multiple interfaces). You can also create abstract classes - classes that can't be instantiated on their own; they must be inherited in other classes. In this article you will learn all these aspects of TypeScript inheritance.