Book Image

JavaScript for .NET Developers

By : Ovais Mehboob Ahmed Khan
Book Image

JavaScript for .NET Developers

By: Ovais Mehboob Ahmed Khan

Overview of this book

If you want to improve responsiveness or the UX in your ASP.NET applications, JavaScript can be a life saver. In an age where server-side operations have shifted to the client, being able to handle JavaScript with confidence and fluency is vital for ASP.NET developers. There’s no point trying to fight it, so start learning with this book. Make sure your projects exceed user expectations. Begin by getting stuck into the basics of JavaScript, and explore the language in the context of ASP.NET Core. You’ll then find out how to put the principles into practice, as you learn how to develop a basic ASP.NET application using Angular 2 and TypeScript. You’ll also develop essential skills required to develop responsive apps, with a little help from AJAX, ensuring that you’re building projects that can be easily accessed across different devices. With guidance on Node.js and some neat techniques to test and debug a range of JavaScript libraries in Visual Studio, you’ll soon be well on your way to combining JavaScript with ASP.NET in a way that’s capable of meeting the challenges of modern web development head-on.
Table of Contents (17 chapters)
JavaScript for .NET Developers
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Middleware


Node.js Express also provides a special routing method, all(), which is not mapped to any HTTP method. But it is used to load Middleware at a path, irrespective of the HTTP method being requested. For example, making HTTP GET and POST requests at http://localhost/middlewareexample will execute the same all() method shown in the following code:

expressApp.all('/middlewareexample', function (req, res) {
    console.log('Accessing the secret1 section ...');
});

Just like in .NET, we have OWIN middleware that can be chained in the request pipeline. In the same way, Node.js Express middleware can also be chained and can be invoked by calling the next middleware with a little change in the function signature. Here is the modified version that takes the next parameter after the response object which provides a handler to the next middleware in the pipeline, defined in a sequence for a particular request path:

expressApp.all('/middlewareexample', function (req, res, next) {
    console.log...