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

Risks of the in-place upgrade

When .NET 4.5 is installed, it effectively replaces the existing .NET 4.0 assemblies in the machine; they are overwritten by a newer version.

Curiously, when we query the runtime version, Environment.Version is still 4.0.30319, having differences only in the build numbers. Basically, it becomes hard for the application to identify if we are running .NET 4.0 or 4.5, which might be necessary if we have to decide which part of the code can or cannot be executed.

And yes, we can build an application on .NET 4.5 and execute it on .NET 4.0, but these might not run properly if it uses some features of the .NET 4.5 framework. Otherwise, building .NET 4.0 applications with .NET 4.5 should not bring any problems.

For avoiding these issues, we should use the <supportedruntime> element, which specifies the versions of the CLR supported by the application with a syntax like the following:

<supportedRuntime version="runtime version" sku="sku id"/>

If this is not found on the application configuration file, the runtime version used to build the application will be used. An example of this configuration is the following:

        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />

With this in place, the application will know that it needs .NET 4.5; if it is not installed, our application will not run and propose to install it.

Note that most of the client applications add this automatically, but we must keep an eye out for it or we might be surprised.