Most developers misuse the facility of exceptions provided by the NET framework. They tend to catch all exceptions when they were expecting only file-based exceptions to be thrown. In some situations, this leads to trapping exceptions which mask state corruption of the managed process. In .NET Framework 4.0, the default implementation has changed for the better, allowing only non-corrupted state exceptions to be handled by default.
Articles Written by Vipul Vipul Patel
The new Windows Phone 7 platform isn't restricted to only C# programming. Microsoft recently released development tools targeting Visual Basic developers. This article discusses how to get the tools and walks through a simple Visual Basic Silverlight project for the Windows Phone 7 platform.
In .NET framework 4.0, a new class, MemoryMappedFile, was introduced to facilitate the editing of large files and inter-process communication. Read along to learn more about this new class.
Windows Phone 7 architecture allows developers to choose between two different frameworks for application development. In this article, we see how easy it is to create a Silverlight based application for the Windows Phone 7 platform.
.NET Framework 4.0 saw a few changes in the classes in the System.IO System.IO namespaces to make the disk I/O operations better. This article provides an insight to these changes.
.NET Framework 4.0 made code contracts first class citizens by introducing System.Diagnostics.Contracts as part of base class libraries. Code contracts offer a way to express state assumptions in applications and take forms of pre-conditions, post-conditions and object invariants. Read more to learn the underlying internals of how code contracts work.