Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Hands-On TypeScript for C# and .NET Core Developers
  • Table Of Contents Toc
  • Feedback & Rating feedback
Hands-On TypeScript for C# and .NET Core Developers

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

By : Francesco Abbruzzese
2.5 (2)
close
close
Hands-On TypeScript for C# and .NET Core Developers

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

2.5 (2)
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)
close
close

Questions

  1. What is the problem solved by namespaces, and what is the JavaScript equivalent of namespaces?
  2. Can you list the main pitfalls of namespaces? How are they solved by modules?
  3. How can you import all symbols exported by the A module without being forced to prefix the names of all symbols in A with another identifier in the subsequent code (for example, if A contains a Person class, we don't want to write something such as new prefix.Person(...), but we would like to write simply new Person(...))?
  4. When is module-resolution performed? At compile time? At runtime?
  5. When and why are non-relative paths needed in import statements?
  6. What is the main advantage of a dynamic import? When is it needed?
  7. Is a dynamic import part of the ES6 specifications?
  8. Can TypeScript's dynamic import be used by a browser that doesn't support JavaScript-native dynamic import? How?
  9. Do...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY