| .NET Data Persistence: SQL Server vs. Matisse vs. FastObjects |
| The Code Project |
| An article with source code examining the development speed and performance capability of .NET, Matisse and FastObjects |
|
| .NET Scheduled Timer |
| The Code Project |
| A timer that easily supports absolute schedules like run at 4:00 AM every day or at 5:00 PM on Fridays |
|
| A Data Access Layer to Persist Business Objects Using Attributes and Reflection |
| The Code Project |
| Then I came up with the idea of creating classes that would say how they should be persisted in the database. I would use attributes to say what database table my object should be persisted to, as well as other attributes to say what are the properties that should be mapped to table columns. From now on to update my code after a change in the solution I would only change the business object class. |
|
| A library to simplify access to image metadata |
| The Code Project |
| A library to simplify access to image metadata. |
|
| A Practical Guide to .NET DataTables, DataSets and DataGrids - Part 2 |
| The Code Project |
| The purpose of this document is to provide a practical guide to using Microsoft’s .NET DataTables, DataSets and DataGrid |
|
| A Practical Guide to .NET DataTables, DataSets and DataGrids - Part 4 |
| The Code Project |
| The purpose of this document is to provide a practical guide to using Microsoft’s .NET DataTables, DataSets and DataGrid |
|
| A simple but handy utility for serializing and de-serializing various data |
| The Code Project |
| Interop various data among native, .NET and Java codes. |
|
| A Simple Usage of Reflection |
| DotNetJunkies |
| Xico takes a quick look at what Reflection is all about and explains what it can do for you. |
|
| Abstracting ADO .NET |
| MSDN |
| With the release of Microsoft® .NET just around the corner, developers are gearing up to take advantage ot the many features, increased interoperability, and better data integration that the new framework promotes. While COM and Visual Basic® 6.0 are still widely used and will likely live on for years to come, I've met many developers who are anxious to get moving with the .NET components. Some of the questions I am asked most often regarding .NET are how developing with ActiveX Data Objects (ADO) 2.x will change under ADO .NET and how can you still abstract ADO into a data service component. So, in this month's Data Points column, I'll try to tackle these issues.
|
|
| Advanced Basics: P2P Comm Using Web Services |
| MSDN |
| Build your own chat client |
|
| Advanced Data Access with ADO.NET and Oracle |
| MSDN |
| Learn how to use ADO.NET 1.1 to retrieve data from complex Oracle data types. |
|
| Advanced Data Mapping in .NET |
| DotNetJunkies |
| In this article, Tin demonstrates 3 automated mechanisms for data mapping: mapping from Database table columns to object properties, mapping from HTML form fields to object properties, mapping from ASP.NET Web controls to object properties. |
|
| An In-Depth Look at the DateTimeFormatInfo Class |
| C#Today |
| The DateTimeFormatInfo (DTFI) class is one of the most important members of the .NET System.Globalization namespace. Although acting mainly as the IFormattable interface for the DateTime structure, DTFI is also informational. You can, for example, find out the names of the days of the week and months of the year in native form, an amazing number of alternate date and time patterns that are acceptable in a particular culture, and which week is the first one of a new year. In addition, DTFI provides the main access to the more than half-dozen calendars supported by .NET. In this article, Bill Hall will show you how easy it is to use the facilities of DTFI, and will gain experience in writing code that functions correctly independently of language and world region. |
|
| An introduction to a post-relational database for .NET, Matisse - Part 3 |
| The Code Project |
| Step by step guide for .NET programming with a Post-Relational Database |
|
| Analyse IL and say hello (or goodbye) to your memory |
| The Code Project |
| Avoid unnecessary variable declaration and redundant instructions, analysing and understanding the compiler and generated IL instructions in a simple example, saving your memory. |
|
| ASP.NET Developer's Cookbook Chapter 3: Custom Controls |
| The Code Project |
| The most common techniques in building custom controls in ASP.NET. |
|
| ASP.NET Localization Part 1: CultureInfo |
| DotNetJunkies |
| The .NET Framework provides built-in mechanisms for localizing applications. ASP.NET internally uses Unicode and the String class of the .NET Framework also uses Unicode. The use of Unicode enables you to easily specify different encoding types for the response data sent to the client. While the .NET Framework will not translate your documents from the language they are written in to a different language, the built-in mechanisms will reconfigure output such as DateTime objects to their appropriate format. |
|
| ASP.NET Validation Controls |
| DotNetJunkies |
| Input validation can be a tricky thing. Ideally we should validate the data on the client side to prevent unnecessary round trips to the server. That requires JavaScript. But not every browser out there processes JavaScript (hard to believe, isn't it). And even still, changing the display characteristics to show errors in the input is not always supported. Not to mention, a slightly unethical person could recreate your page, and bypass the validation all together. Ugh! This leaves us with server-side valida |
|
| Asynchronous Context Processor |
| The Code Project |
| Asynchronous message processing infrastructure for .NET applications. |
|
| Auto-Generating Wrapper Classes for Stored Procedures, Part 1: Using the AutoSproc Tool |
| MSDN |
| Get an overview of the AutoSproc code generation tool and how it works. The AutoSproc tool (based on classes exposed from the System.Reflection.Emit namespace) saves you time by using reflection to auto-generate wrapper classes for stored procedure calls. |
|
| Automated Generation of Table Columns, Class Properties, and Form Field Mapping with C# Reflection |
| C#Today |
| In this article, Tin Lam shows how to use reflection to help us with complex mappings. Reflection allows us to examine assemblies and types at runtime, and find out everything about that type. We will also see how to dynamically extract the type information, and then carry out automated mappings between database table columns, HTML form fields and class properties. |
|
| BetterCalendar WebControl |
| The Code Project |
| A replacement for the System.Web.UI.WebControls.Calendar control. |
|
| Boxing and Performance of Collections |
| C# Corner |
| A few days ago, a post alerted me on C# Corner discussion forums about collection and performance issues during boxing and unboxing. A collection such as an ArrayList stores data as 'generic objects' and boxing and unboxing operations may be used to store and retrieve data from a collection. During process of boxing and unboxing, it may be possible that the performance of conversion is being affected due the large number of items stored in a collection. I've done a bit of research over this and here is my conclusion. |
|
| Building a Custom Data Provider for Use with the .NET Data Access Framework |
| MSDN |
| The System.Data.dll assembly in the .NET Framework contains namespaces whose base classes can be used to create custom data providers. These namespaces also define a number of data access interfaces and base classes that let developers create data providers that will interoperate with other custom providers. Using the ADO.NET classes Connection, Command, DataReader, and DataAdapter, writing a provider is easier than writing one for OLE DB. This article explains these classes and their implementation, and how they can be used to write a variety of different kinds of data providers. |
|
| Building a DataNavigator Control |
| MSDN |
| The list of ASP.NET rich data-bound controls is a long one, but it's not all-encompassing. You won't find any Microsoft® .NET counterpart for the Data control—a scrollable and updateable binding context that data-bound controls could rely on to refresh their user interface. The original Data control allowed for simple movements—first, next, previous, and last. It worked on top of a Recordset object and exposed the UpdateRecord method to save changes according to the capabilities of the currently selected type of cursor. While not the perfect programming tool, the Data control was especially good at building simple user interfaces for tables used internally for administrative purposes. |
|