I heard that COM objects no longer need to be registered on the server?Is it true!!!!!!!!!!!!!!!!

Hi , Yes and No. Legacy COM objects still need to be registered on the server before they can be used. COM developed using the new .NET Framework will not need to be registered. Developers will be able to auto-register these objects just by placing them in the ‘bin’ folder of the application.

Can .NET Framework components use the features of Component Services?

Yes,sure, you can use the features and functions of Component Services from a .NET Framework component.

How do you create threading in .NET?is it possible!!!!!!!!!!!!!!!!!!1

Yes it is.Thread basics using followings:

How to Create thread; use System.Thread() class and create an instance.

How to Join thread; use object.Join() to join threads.

How to Suspend thread; use object.Sleep(<No of seconds>) to Suspend thread.

How to Kill thread; use object.Abort() to Suspend thread.

Using Interlocked class which uses Increment and decrement method to increment and decrement values.

hi forum,
What are ADSI Directories? please give details!

hello member giving you details…
Active Directory Service Interfaces (ADSI) is a programmatic interface for Microsoft Windows Active Directory. It enables your applications to interact with diverse directories on a network, using a single interface. Visual Studio .NET and the .NET Framework make it easy to add ADSI functionality with the DirectoryEntry and DirectorySearcher components.
Using ADSI, you can create applications that perform common administrative tasks, such as backing up databases, accessing printers, and administering user accounts. ADSI makes it possible for you to:
• Log on once to work with diverse directories. The DirectoryEntry component class provides username and password properties that can be entered at runtime and communicated to the Active Directory object you are binding to.
•Use a single application programming interface (API) to perform tasks on multiple directory systems by offering the user a variety of protocols to use. The DirectoryServices namespace provides the classes to perform most administrative functions.
•Perform “rich querying” on directory systems. ADSI technology allows for searching for an object by specifying two query dialects: SQL and LDAP.
•Access and use a single, hierarchical structure for administering and maintaining diverse and complicated network configurations by accessing an Active Directory tree.
•Integrate directory information with databases such as SQL Server. The DirectoryEntry path may be used as an ADO.NET connection string provided that it is using the LDAP provider.

What is Application Domain?

 hello giving you a bit of info think it might be useful…
The primary purpose of the App.Domain is to isolate an application from other applications. Win32 processes provide isolation by having distinct memory address spaces. This is effective, but it is expensive and doesn’t scale well. The .NET runtime enforces AppDomain isolation by keeping control over the use of memory – all memory in the AppDomain is managed by the .NET runtime, so the runtime can ensure that AppDomains do not access each other’s memory.
Objects in different application domains communicate either by transporting copies of objects across application domain boundaries, or by using a proxy to exchange messages.
MarshalByRefObject is the base class for objects that communicate across application domain boundaries by exchanging messages using a proxy. Objects that do not inherit from MarshalByRefObject are implicitly marshal by value. When a remote application references a marshal by value object, a copy of the object is passed across application domain boundaries.

How does an AppDomain get created?

AppDomains are usually created by hosts. Examples of hosts are the Windows Shell, ASP.NET and IE. When you run a .NET application from the command-line, the host is the Shell. The Shell creates a new AppDomain for every application.
AppDomains can also be explicitly created by .NET applications