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)

Chapter 7

  1. Just three. Entries depend only on the main bundles that must be created, not on their dependencies.
  2. Yes, it is possible, but the names of the modules that might be loaded dynamically must be computable at bundling time. This way, WebPack knows which modules it must process. Usually, they are passed as constant strings in the import instruction, and the decision of whether or not to load each module is taken with if.
  3. By letting the WebPack configuration object be returned by an arrow function that receives the environment as its argument. See the Production and development configurations section.
  1. Yes, it is. Each entry may also be passed an array of independent files.
  2. Once Microsoft.AspNetCore.SpaServices is installed and configured, it is enough to set the HotModuleReplacement property of the WebPackDevMiddlewareOptions option object to true. Then it is necessary...