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)

Summary

As in several languages, such as C# and C++, TypeScript namespaces were conceived to avoid name collisions among different libraries and application parts in large code bases. However, they don't solve another important problem of large code bases: dependency-tracking. TypeScript modules solve both these problems, but projects based on modules require an advanced knowledge of JavaScript bundlers, and are more difficult to configure and build. Namespaces should be preferred in simpler applications based mainly on server-side processing that uses JavaScript to improve HTML page graphics, while modules should be preferred in complex, rich-client applications, such as SPAs, that move the whole presentation layer to the client side.

TypeScript modules mimic ES6-native modules but may also generate JavaScript code based on other non-native module systems, such as AMD, CommonJS...