ASP.NET Core and Angular Book: Reader Feedback Wanted! Help us to create the fifth edition of the ASP.NET Core and Angular book series answering to a short survey

ASP.NET Core 5 and Angular - Fourth Edition

These days I’m starting to work on the next edition of my ASP.NET Core and Angular book: if everything goes well, it will be the fifth (!) one.

If the ASP.NET Core and Angular teams will respect their release schedule the new book will mostly likely deal with ASP.NET Core 6 and Angular 13, which are expected to get released in Q4 2021.

Without further ado, here’s a brief list of some new features that I plan to add to the 5th edition of the book:

  • Swagger. A brand new chapter dedicated to Swagger, the world’s most popular design, development & documentation standard for RESTful APIs using the Swashbuckle.AspNetCore package.
  • GraphQL. A brand new chapter to explore GraphQL, the well known open-source data query and manipulation language for APIs using the GraphQL.NET SDK, Altair UI and the Apollo Angular client.
  • SignalR. A brand new chapter to introduce SignalR, an awesome open-source software library for Microsoft ASP.NET that allows the back-end server (ASP.NET) to send asynchronous notifications to the front-end client (Angular), thus adding real-time web functionality to web applications, using the ASP.NET Core SignalR library.
  • Protractor. A new addition to Chapter 9: ASP.NET Core and Angular Testing where we’ll talk about Protractor, and end-to-end testing framework for Angular applications.

And the list goes on: the new edition will also feature a full revamp of all previous chapters, an extensive overview of the many Entity Framework Core 6 new features, and much more!

Together with Packt I have prepared a short survey to collect reader feedback on the latest edition: what topics you liked the most, what you would like to find in the next edition, and so on. If you feel like helping us you can do so using this link.

Thank you for taking time to help us!

What’s new in ASP.NET

ASP.NET Core 6 preview 6 has been released less than a week ago and is packed with many great new improvements. Here’s a full list of what’s new in this preview release:

  • Improved Blazor accessibility
  • Required Blazor component parameters
  • Efficient byte array transfers for JavaScript interop
  • Optional parameters for view component tag helpers
  • Angular template updated to Angular 12
  • OpenAPI support for minimal APIs
  • Inject services into minimal APIs without [FromServices] attribute
  • Configure the accept socket for Kestrel
  • IHttpActivityFeature
  • Long running activity tag for SignalR connections
  • WebSocket compression
  • SignalR WebSockets TestServer support
  • New OnCheckSlidingExpiration event for controlling cookie renewal
  • ClientCertificateMode.DelayCertificate

What’s new in Angular

The official Angular roadmap hasn’t been updated for a while, however there are a lot of upcoming features that have already been announced this year:

  • Better Developer Ergonomics with Strict Typing. Implementing a stricter type of checking for reactive forms allows developers to catch more issues during development time.
  • Reduce Framework Overhead. Removing legacy View Engine for the smaller Angular conceptual overhead (lower maintenance cost, lower complexity of codebase, and a smaller package).
  • Improved Text Times and Debugging. Automatic test environment tear down improves test time and creates better isolation across tests. The goal is to change TestBed to automatically clean up and tear down the test environments after each test run.
  • Optional NgModulars. Optional NgModulars allow developers to develop standalone components and implement an alternative API to declare the component’s compilation scope.
  • Support Directives to Host Elements. Adding directives to host elements allows developers to augment their components with more behaviors without inheritance.
  • Angular Compiler as a PlugIn (tsc). When making this a reality, the developers substantially improve build performance and reduce maintenance costs.
  • Ergonomic Component Level Code-Splitting APIs. Applying a more granular code-splitting component level is one way to improve the initial load time.

Conclusion

That’s it, at least for now: if you want to help me to further improve the book, be sure to take the survey and let us hear your suggestions. Furthermore, if you want to get the latest updates, feel free to subscribe to our newsletter and to follow the current edition’s official repository on GitHub.

 

About Ryan

IT Project Manager, Web Interface Architect and Lead Developer for many high-traffic web sites & services hosted in Italy and Europe. Since 2010 it's also a lead designer for many App and games for Android, iOS and Windows Phone mobile devices for a number of italian companies. Microsoft MVP for Development Technologies since 2018.

View all posts by Ryan

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.