| "Can't create a child list" error message when you open a form in Visual Studio .NET |
| Microsoft Support |
|
(816799) - When you delete the table that is bound to a control form of the DataSet Schema and then save the project in Microsoft Visual Studio .NET, you may receive the following error message when you open the form in Design view: Can't create a child list for...
|
|
| "Can't create a child list" error message when you open a form in Visual Studio .NET |
| Microsoft Support |
| (816799) - When you delete the table that is bound to a control form of the DataSet Schema and then save the project in Microsoft Visual Studio .NET, you may receive the following error message when you open the form in Design view: Can't create a child list for... |
|
| "Can't create a child list" error message when you open a form in Visual Studio .NET |
| http://www.kbalertz.com/ |
| (816799) - When you delete the table that is bound to a control form of the DataSet Schema and then save the project in Microsoft Visual Studio .NET, you may receive the following error message when you open the form in Design view: Can't create a child list for... |
|
| .NET Anatomy - ADO.NET in Beta2 : Part 1 |
| DotNetJunkies |
| This article reviews the ADO.NET object model found in Microsoft’s .NET Framework Beta2. The information presented here will be useful both to programmers who worked with Beta1 and also, to those just starting with the framework. |
|
| .NET Anatomy - ADO.NET in Beta2 : Part 2 |
| DotNetJunkies |
| In my last article I reviewed the ADO.NET object model as it is presented in the .NET framework Beta2. To put this information to practical use, this article will provide a walkthrough of how to use Microsoft's newest set of developer tools, found in Visual Studio.NET to create a working Web Application that accesses an SQL database. |
|
| .NET Anatomy - Data Concurrency in ADO.NET, Part I |
| DotNetJunkies |
| This article is the beginning of a multi-part article that discusses data concurrency in ADO.NET and reviews how the ADO.NET model supports multi-user scenarios where data may be updated at the server while an ADO.NET client is using that data. |
|
| .NET Anatomy - Data Concurrency in ADO.NET, Part II |
| DotNetJunkies |
| This is the second article in a series covering the subject of Concurrency in ADO .NET. Concurrency is the method by which many users are able access and change the same data simultaneously without being concerned that they are overwriting each others work. |
|
| .NET Anatomy - Data Concurrency in ADO.NET, Part II |
| DotNetJunkies |
| This is the second article in a series covering the subject of Concurrency in ADO .NET. Concurrency is the method by which many users are able access and change the same data simultaneously without being concerned that they are overwriting each others work. The architects of the .NET Framework made a design decision that the DataSet object assumes that Optimistic Concurrency as the default method of concurrency. |
|
| .NET Anatomy - Data Concurrency in ADO.NET, Part III |
| DotNetJunkies |
| In the two previous articles on this subject we have looked at how the ADO.NET DataSet object contains built-in support for concurrency operations. This functionality helps the developer to build applications that keep users from overwriting each other’s data accidentally. The implementation is open and flexible and so what I will be showing you here can be tailored to your own requirements |
|
| .NET Anatomy Part II: Creating the ADO.NET Component |
| DotNetJunkies |
| This three part article shows, step-by-step, how to use Visual Studio .NET to create templated controls visually, without writing code and then explores the code that is generated as a result. In Part II, Barton explains how to create the ADO.NET component writing less than ten lines of code. |
|
| .NET Anatomy Part III: Creating the Templated Control |
| DotNetJunkies |
| This three part article shows, step-by-step, how to use Visual Studio .NET to create templated controls visually, without writing code and then explores the code that is generated as a result. In the final part of this article, Barton turns his attention to the ASP.NET portion of the project, creates the templated control and wraps things up. |
|
| .NET Connector for Microsoft Outlook |
| The Code Project |
| Export Microsoft Outlook data using XML DataSets and the Outlook COM Object Library. |
|
| .NET Data Access Performance Comparison |
| http://aspalliance.com/ |
| This article attempts to compare several different data access techniques through the use of a stress testing tool. DataTables and DataReaders are compared with a number of different variables, and recommendations for best practices are provided. |
|
| .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 Remoting Using Broker Pattern |
| The Code Project |
| .NET remoting using Broker pattern. |
|
| .NET Remoting Using Broker Pattern |
| The Code Project |
| .NET remoting using Broker pattern. |
|
| .NET Tools: Ten Must-Have Tools Every Developer Should Download Now |
| MSDN |
| 10 Tools you can use to make your development easier, faster and more fun! |
|
| 3D Pie Chart |
| The Code Project |
| Class library for drawing 3D pie charts |
|
| A C# Web Spider written as a Web Service |
| C#Today |
| A Web Spider is a program that is used to navigate sites, follow links and collect various information. It is sometimes called a Web Robot. In this article. ST Tan & Aldy Karna discuss the subject, and show how a Web Spider can be written in C#. |
|
| A Charting Custom Control using Microsoft OWC |
| The Code Project |
| This is a .NET custom control for web-based charting using Office Web Component technology. |
|
| 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 Database Admin Tool in 20 Lines of C# Code |
| ASP Alliance |
| This example illustrates how to create a one page database administration tool with only 20 lines of C# code. Using this example, you can enter almost any Sql statement into a text box and execute the statement against any tables in your database. You can view the results of a SELECT in a DataGrid or the see the affects of UPDATE, INSERT and DELETE statements. |
|
| A DropDownList, EditItemTemplate, using Access, and HttpSessionState...Part 3 |
| DotNetJunkies |
| Here we are at part three of this article! In this part we will be adding one new feature to the code! Instead of making a call to the database to get the data on each request we are going to be saving the <b>DataSet</b> into session state. We will not only be populating the <b>DataGrid</b> and <b>DropDownList</b> controls from this <b>DataSet</b>, but we will also be saving all the edits done by the user. This means that after the <b>DataSet</b> is initially created and put into session state there will be |
|
| A DropDownList, EditItemTemplate, using Access, and HttpSessionState...Part 4 |
| DotNetJunkies |
| In this article I will demonstrate how you
can save the changes made to the memory resident <b>DataSet</B>. |
|
| A First Look at ObjectSpaces in Visual Studio "Whidbey" |
| MSDN |
| An interesting new feature in Visual Studio "Whidbey" is ObjectSpaces, an Object/Relational mapping tool fully integrated with ADO.NET. You design application features using objects, and ObjectSpaces reads and writes to data sources using SQL statements. |
|
