With a number of clients, I have been provided a sample format for a transactions along with instructions to develop a process to load it into a database as quickly and painlessly as possible. This usually comes with the requirements that the XML data file can have any number of records from 1 to n. This example demonstrates the most efficent and scalable way that I have found to solve this. Not to mention that it can be maintained without rebuilding the solutions each time the data format changes.
Most applications deal with data of some type or another, where the source of the data often resides in a database. Yet for a variety of reasons the shape of the data in the database is often different from the model that the application interacts with. This article describes working with data in a database through a virtual "Conceptual Model" more appropriate for the application.
As consultants, we know we're probably dealing with a scaling issue when the application performs well in the test environment but poorly in the real world. Usually, the only difference between the two is the number of simultaneous users. If the application performed poorly all the time, you would have a performance problem rather than a scaling problem. There are three strategies available that you can employ in order to improve scaling: specialization, optimization, and distribution. How you apply them will vary, but the actual strategies are straightforward and consistent.
You can create extensible apps using the Managed Extensibility Framework (MEF), which is built right into the .NET Framework 4. We'll walk through an example to compare plug-in implementations using both MEF and Inversion of Control frameworks.
This article shows you how easy it is to use a build framework such as MSBuild or TeamCity to build .NET software. It also demonstrates how to add Continuous Integration (CI) with .NET applications to an Agile ALM CI ecosystem that can also integrate other artifact types, such as Java.