ASP.Net web forms, as the webpages are officially known, can become cumbersome to handle when they grow richer. The first line of defense, in such cases, is offered by the Browser Debugging Tools. Read on to find out more about such tools and how they help.
In this new installment, you'll discover how to write an even more robust version of a debugger visualizer using WIndows Presentation Foundation (WPF). You'll learn how to visualize additional data types as well as how to change the value of variables.
There are lots of good examples of creating a debugger visualizer for Visual Studio, but one thing that this is common is that all of them are written using Windows form. It is, however, possible to make a debugger visualizer in WPF, and thus display data in a much more sophisticated way using modern technology.
This article introduces code contracts that specify statements in .NET programs that must prove valid.
Check-in policies help enforce your organization's development methodology and ensure that the code being checked in passes the necessary quality requirements. In addition to using the pre-defined check-in policies, you can create custom ones.
Simplify finding the entry you need from an event log.
The Transactional File System (TxF), which allows access to an NTFS file system to be conducted in a transacted manner through extensions to the Windows SDK API. MFC 10, has been extended to support TxF and related technologies. This support allows existing MFC applications to be easily extended to support kernel transactions.
The original release of the .NET Framework included collections as .NET was introduced to the Microsoft programming world. The .NET Framework 2.0 introduced generics to complement the System.Collections namespace and provide a more efficient and well performing option. Read on to learn more...
Apart from Hashtables, queues and stacks are probably the most common Collection classes. This article explains the ins and outs of queues and stacks.
WCF implementations normally take two different approaches; a Document style or an API style. Document style implementations are more flexible and often easier to extend and version. Also, Document style or rather, Message Contract service implementations, work well between systems with a shared message assembly. Jeffrey Juday guides you through architecting a WCF Message Contract implementation.
