In a typical ASP.NET MVC application, the controller sends model data to the view and the view then renders the data in the required form. Bipin Joshi shows you how child action methods can be used to render markup dynamically.
Asynchronously running code can improve the overall performance and responsiveness of your web application. In ASP.NET 4.5 web forms applications you can register asynchronous methods with the page framework. The ASP.NET page framework and .NET 4.5 asynchronous programming support then executes the operations in asynchronous fashion. This article shows how this can be done.
For security reasons browsers don't allow cross-domain communication. However, in some legitimate situations cross-domain communication becomes necessary. A common work-around for this restriction is to use JSON with Padding or JSONP. In this article you will learn how JSONP can be used in an ASP.NET MVC application.
Unhandled exceptions in the Web API controller class are often indicated as HTTP status code 500, i.e. Internal Server Error. This generic error message is of little use to the client. Bipin Joshi explains how to use Web API to fine tune and customize the HTTP errors that are sent to the client browser.
Earlier releases of ASP.NET validation controls depended upon JavaScript, emitted by the ASP.NET web form framework. Unobstructive validation makes use of the data-* attributes of HTML5 for validation purposes. Bipin Joshi shows you how the new unobstructive validation features work for Web Forms.
Joydip Kanjilal takes a look at the 10 best practices to follow for the best and most efficient use of ASP.NET MVC Framework 4.
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...
There are millions of Namespaces in the .NET Framework. Coming from a VB 6 background, I was accustomed to arrays and arrays only. Luckily all has changed with .NET, in that the .NET Framework supports Collections, which as its name implies, is a collection of objects that you can store in a certain manner.
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.
