Book Image

Hands-On TypeScript for C# and .NET Core Developers

By : Francesco Abbruzzese
5 (1)
Book Image

Hands-On TypeScript for C# and .NET Core Developers

5 (1)
By: Francesco Abbruzzese

Overview of this book

Writing clean, object-oriented code in JavaScript gets trickier and complex as the size of the project grows. This is where Typescript comes into the picture; it lets you write pure object-oriented code with ease, giving it the upper hand over JavaScript. This book introduces you to basic TypeScript concepts by gradually modifying standard JavaScript code, which makes learning TypeScript easy for C# ASP.NET developers. As you progress through the chapters, you'll cover object programming concepts, such as classes, interfaces, and generics, and understand how they are related to, and similar in, both ES6 and C#. You will also learn how to use bundlers like WebPack to package your code and other resources. The book explains all concepts using practical examples of ASP.NET Core projects, and reusable TypeScript libraries. Finally, you'll explore the features that TypeScript inherits from either ES6 or C#, or both of them, such as Symbols, Iterables, Promises, and Decorators. By the end of the book, you'll be able to apply all TypeScript concepts to understand the Angular framework better, and you'll have become comfortable with the way in which modules, components, and services are defined and used in Angular. You'll also have gained a good understanding of all the features included in the Angular/ASP.NET Core Visual Studio project template.
Table of Contents (16 chapters)

Namespaces

In several examples in this book, the code was enclosed inside a function body:

(function () {
//code here
})();

This way, all symbols being declared inside a function body are local to that function and are not visible outside of the function body in other TypeScript files. This is a best practice in JavaScript. In fact, global symbols shared between several files, possibly written by different people, may cause unwanted interactions, thereby causing hard-to-find bugs.

Therefore, global symbols must be carefully planned with the whole development team. It is best practice to organize all symbols that must be shared among several files into trees rooted in a few global symbols that are agreed upon by the whole development team. For instance, jQuery is the root symbol of the jQuery library and all public symbols of this library are available as nested properties of...