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)

Installing a test framework – Jasmine

The simplest way to test a TypeScript library is by running all tests in Node.js, since it may work without a web server and a browser. Another advantage of running tests in Node.js is that library packages installed with npm, such as jQuery, may work as they are, while browser-based testing would require the use of a bundler since browsers do not support the Node.js-based module resolution algorithm required by npm packages.

On the other hand, tests that succeed under Node.js might fail on some browsers due to compatibility problems, so when Node.js testing is chosen, some browser-based compatibility tests on all dangerous features that might not be supported by all browsers are required.

Browser-based testing will be applied to Angular projects as described in the Testing section of Chapter 13, Navigation and Services. This and the...