check these links

http://www.awprofessional.com/articles/article.asp?p=170917
http://aspnet.4guysfromrolla.com/articles/121504-1.aspx
http://aspnet.4guysfromrolla.com/articles/121504-1.2.aspx
http://www.dotnetjohn.com/webcontrols.aspx
http://www.asp101.com/articles/stuart/dataview/default.asp
http://samples.gotdotnet.com/quickstart/howto/doc/adoplus/FilterData.aspx
http://www.error-bank.com/microsoft.public.dotnet.framework.adonet/79191_Thread.aspx
http://www.c-sharpcorner.com/Code/2003/July/DynamicallyCreateASPNETControls.asp
http://www.dotnetjohn.com/dotnet20.aspx
http://www.xmlforasp.net/codeSection.aspx?csID=51
http://authors.aspalliance.com/wisemonk/view.aspx?id=AD032102
http://www.dotnetjohn.com/articles.aspx?articleid=56
http://www.dotnetjohn.com/articles.aspx?articleid=31
http://www.google.co.in/search?q=bind+listbox+to+a+dataview&hl=en

Interface or Abstract Classes

An abstract class is a class that cannot be instantiated, but must be inherited from. An abstract class may be fully implemented, but is more usually partially implemented or not implemented at all, thereby encapsulating common functionality for inherited classes.

An interface, by contrast, is a totally abstract set of members that can be thought of as defining a contract for conduct. The implementation of an interface is left completely to the developer.

Both interfaces and abstract classes are useful for component interaction.


Here are some recommendations to help you to decide whether to use an interface or an abstract class to provide polymorphism for your components :

• If you anticipate creating multiple versions of your component, create an abstract class. Abstract classes provide a simple and easy way to version your components. By updating the base class, all inheriting classes are automatically updated with the change. Interfaces, on the other hand, cannot be changed once created. If a new version of an interface is required, you must create a whole new interface.
• If the functionality you are creating will be useful across a wide range of disparate objects, use an interface. Abstract classes should be used primarily for objects that are closely related, whereas interfaces are best suited for providing common functionality to unrelated classes.
• If you are designing small, concise bits of functionality, use interfaces. If you are designing large functional units, use an abstract class.
• If you want to provide common, implemented functionality among all implementations of your component, use an abstract class. Abstract classes allow you to partially implement your class, whereas interfaces contain no implementation for any members.

alternative editors or IDEs for C#

To find alternative editors, you can check computer stores or computer mail-order catalogs. Another place to look is in the ads in computer programming magazines. The following are a few editors that were available at the time this book was written:

CodeWright. CodeWright is an editor that provides special support for ASP, XML, HTML, C#, Perl, Python, and more. It is located at www.premia.com.
EditPlus. EditPlus is an Internet-ready text editor, HTML editor, and programmer's editor for Windows. Although it can serve as a good replacement for Notepad, it also offers many powerful features for Web page authors and programmers, including the color- coding of code. It is located at www.editplus.com.
JEdit. JEdit is an Open-Source editor for Java; however, it can be used for C#. It includes the capability of color-coding the code. It is located at http://jedit.sourceforge.net.
Poorman IDE by Duncan Chen. Poorman provides a syntax- highlighted editor for both C# and Visual Basic .NET. It also enables you to run the compiler and capture the console output so you don't need to leave the Poorman IDE. Poorman is located at www.geocities.com/duncanchen/poormanide.htm.
SharpDevelop. SharpDevelop is a free editor for C# projects on Microsoft's NET platform. It is an Open-Source Editor (GPL), so you can download both source code and executables from www.icsharpcode.net.

New C# 2005 Overview Released

Microsoft has released a new functional overview of the new features available in C# 2005 (Whidbey). Improvements include language enhancements, productivity enhancements, debugger features, and new platform features.

C# 2.0 introduces several language extensions, including Generics, Anonymous Methods, Iterators, Partial Types, and Nullable Types.

Generics permit classes, structs, interfaces, delegates, and methods to be parameterized by the types of data they store and manipulate. Generics are useful because they provide stronger compile-time type checking, require fewer explicit conversions between data types, and reduce the need for boxing operations and run-time type checks.

Anonymous methods allow code blocks to be written “in-line” where delegate values are expected. Anonymous methods are similar to lambda functions in the Lisp programming language. C# 2.0 supports the creation of “closures” where anonymous methods access surrounding local variables and parameters.

Iterators are methods that incrementally compute and yield a sequence of values. Iterators make it easy for a type to specify how the foreach statement will iterate over its elements.
Partial types allow classes, structs, and interfaces to be broken into multiple pieces stored in different source files for easier development and maintenance. Additionally, partial types allow separation of machine-generated and user-written parts of types so that it is easier to augment code generated by a tool.

Nullable types represent values that possibly are unknown. A nullable type supports all values of its underlying type plus an additional null state. Any value type can be the underlying type of a nullable type. A nullable type supports the same conversions and operators as its underlying type, but additionally provides null value propagation similar to SQL.

Productivity Enhancements:
Check out the link http://msdn.microsoft.com/vcsharp/2005/overview/productivity/


Debugger Enhancements:
Check out the link
http://msdn.microsoft.com/vcsharp/2005/overview/debugger/

Platform Enhancements:
Check out the link
http://msdn.microsoft.com/vcsharp/2005/overview/platform/

Microsoft products using the .NET Framework

In the comments of Scott Hanselman's blog posts on why VB developers don't switch/migrate/convert to VB.NET, someone replied with the following:
So what application has Microsoft written totally in .NET that is worth a [expletive]? Visual Studio - NO, Office - NO, Notepad - NO, Calc - NO. Why haven't they? .....
Here's my response. While the .NET Framework hasn't been around for a long period of time (shiping in February 2002), there is quite a lot of work being done by different teams to use the .NET Framework across Microsoft's product line. Below is a quick list of just some of the ways we're using managed code in products that ship today and how we plan to use managed code in the future.
Windows Client
Windows XP Pro/Home was released before the .NET Framework which is why it was not included in the box. That being said, Soma points out the 70+ million who have downloaded the .NET Framework using Windows Update (note that the 70M number includes all versions of Windows). In fact, there is a lot of debate about why we didn't include Windows XP Service Pack 2 (XP SP2) with the .NET Framework, although most feedback agrees that we should not require installing new features in a service pack that don't relate to security/bug fixes.
Windows XP Pro Tablet PC Edition includes the .NET Framework and the Tablet API is written using the .NET Framework.
Windows XP Media Center Edition includes the .NET Framework and includes MCE-specific applications written using the .NET Framework.
Windows "Longhorn" dramatically increases the amount of managed Windows code including components like WinFx, an all managed API, "Avalon", a managed presentation layer, and "Indigo" a messaging stack, all using managed code.
Windows Server
Windows Server 2003 shipped with the .NET Framework 1.1. New features like Sharepoint Team Services and UDDI Services are written in managed code and require the .NET Framework.
Small Business Server 2003 shipped with the .NET Framework 1.1 and includes some SBS-specific applications like Remote Web Workplace and the Backup Snap-in written in managed code.
OfficeWhile Office is a little behind in adopting the .NET Framework, you'll still find the .NET Framework in use, athough probably not as much as you would probably want. Then again, Office is also expanding itself from being stand alone applications to a fully integrated set of tools for collaboration as witnessed with the Microsoft Office System, and our server products with Web front ends pretty much all use ASP.NET.
Office 2003 Professional Edition includes the .NET Framework, but I believe this is an optional install and is primarily geared for using FrontPage 11 with ASP.NET. Outlook's new Business Contact Manager is primarily written using managed code and requires the .NET Framework.
SharePoint Portal Server 2003 is written using ASP.NET.
Windows Server System
SQL Server 2000 was released before the .NET Framework. Even so, managed providers for SQL Server 7/2000 were included in the .NET Framework 1.0/1.1.
SQL Server Reporting Services shipped after SQL Server 2000, and is primarily written in managed code.
SQL Server 2005 (“Yukon”) will natively host the .NET Framework 2.0, meaning you can write managed database objects like user defined types, stored procedures, triggers, and more in managed code.
Exchange 2003 included managed code for it's mobile UI. Outlook Mobile Access is written in managed code using ASP.NET mobile controls.
BizTalk 2004 has parts written in managed code.
Commerce Server 2002 has parts are written in managed code.
Content Management Server 2002 has parts are written in managed code.
MSN Messenger Server includes a presence server and admin/config tools written in managed code.
Microsoft Business Network has parts written in managed code and requires .NET Framework 1.1.
MS-CRM has parts written in managed code.
Speech Server 2004 has parts written in managed code.
Developer Tools
.NET Framework 1.0/1.1 has parts written in managed code.
.NET Framework 2.0 has parts written in managed code
Visual Studio .NET 2002/2003 has parts written in managed code.
Visual Studio 2005 has parts written in managed code.
ASP.NET Web Matrix is fully written in managed code.
Microsoft Web Properties using the .NET Framework
www.msn.com
www.microsoft.com
msdn.microsoft.com
www.gotdotnet.com
uddi.microsoft.com
www.xbox.com
MapPoint XML Web Service
Microsoft Internal applications using the .NET Framework
Account Explorer
HeadTrax
Consensus
MS Contract
eSupport
Enterprise Product Roadmap (EPR) Explorer
TSP Academy Virtual Instructor
Country Manager Content
TANLink Contributor and TanLink Explorer
Contoso Enterprise Demo v2 – Hotel Desk

What is Application Pools in Windows 2003

An application pool is a configuration that links one or more
applications to a set of one or more worker processes. Because applications in
an application pool are separated from other applications by worker process
boundaries, an application in one application pool is not affected by problems
caused by applications in other application pools.

By creating new application pools and assigning Web sites and applications to them, you can make your server more efficient and reliable, as well as making your other applications always available, even when the worker process serving the new application pool has problems.

What is a Release Candidate of Software Products?

A step in the development process. After the software is feature-set complete and tested. A Release Candidate is created and tested. If testing of the Release Candidate reveals no new bugs, the software is released for sale.

What is a Release Candidate of Software Products?

A step in the development process. After the software is feature-set complete and tested. A Release Candidate is created and tested. If testing of the Release Candidate reveals no new bugs, the software is released for sale.

Go to the Below Link to See the Creator of Programing Languages :

http://khason.biz/blog/2004/12/why-microsoft-can-blow-off-with-c.html