Book Image

Microsoft .NET Framework 4.5 Quickstart Cookbook

By : Jose Luis Latorre
Book Image

Microsoft .NET Framework 4.5 Quickstart Cookbook

By: Jose Luis Latorre

Overview of this book

With about ten years since its first release, Microsoft's .NET Framework 4.5 is one of the most solid development technologies to create casual, business, or enterprise applications. It has evolved into a very stable framework and solid framework for developing applications, with a solid core, called the CLR (Common Language Runtime) Microsoft .NET Framework 4.5 includes massive changes and enables modern application and UI development."Microsoft .Net Framework 4.5 Quickstart Cookbook" aims to give you a run through the most exciting features of the latest version. You will experience all the flavors of .NET 4.5 hands on. The “How-to” recipes mix the right ingredients for a final taste of the most appetizing features and characteristics. The book is written in a way that enables you to dip in and out of the chapters.The book is full of practical code examples that are designed to clearly exemplify the different features and their applications in real-world development. All the chapters and recipes are progressive and based on the fresh features on .NET Framework 4.5.The book will begin by teaching you to build a modern UI application and improve it to make it Windows 8 Modern UI apps lifecycle model-compliant. You will create a portable library and throttle data source updating delays. Towards the end of the book, you will create you first Web API.
Table of Contents (19 chapters)
Microsoft .NET Framework 4.5 Quickstart Cookbook
About the Author
About the Reviewers

Throttling data source update delays

With WPF 4.5, we can now control how the data source that is bound to a part of the UI, gets updated. The best example here is a slider bound to a value, which, for example, has to perform a calculation. With WPF 4.0, the property setter was called for every changed event that was launched by the binding in place and, if we didn't do anything to prevent the excessive calculations, we could end with a responsiveness problem. This could be even worse if some calculation was being performed in response, such as updating the total price.

Now, this doesn't happen, as we can control the delay after the property stops changing, before updating the source. This means that we can change a UI element and we can control how the bound property gets updated. Adding a delay to it will benefit our performance, so that thousands of updates cannot be thrown.

In the slider example, its PropertyChanged event was invoked many times for every movement. Now we can instruct it...