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)

Questions

  1. How many entries are needed in Webpack.Config.js to get three separate bundles that reference a total of 30 dependencies?
  2. Is it possible to use dynamic import() on target browsers that do not support it by using WebPack? Why? If yes, are there limitations?
  3. How does one configure Webpack.Config.js to receive information on the environment it was called in (production or development)?
  4. Is it possible to bundle completely independent files?
  5. How does one enable Hot Module Replacement in ASP.NET Core projects?
  6. Which plugins may be used to optimize bundles with WebPack 4?
  7. Why is the style-loader recommended during development?
  8. How does one automatically invoke WebPack in production mode when an ASP.NET Core application is published?
  9. What is needed to make WebPack-created source maps compatible with the Visual Studio debugger?
  10. Which configuration property must be customized...