Wonderful..Works great by this..Thanks to all others

Favourite quote: In youth we learn, In age we understand.

Sunil, In what way it has helped you more? Can you share your thoughts more please?

Favourite quote: In youth we learn, In age we understand.

I have a winform where I dropped Backgroundworker control and running some loop in DoWork event handle. At the same time I am also within DoWork, I am calling "ReportProgress" method to update my ProgressBar. I thought as my work is going on within DoWork, I can click on other areas of Form and basically since its BackgroundWorker, my other GUI should be responsive but my whole Machine is frozen till "DoWork" finishes. What I am doing wrong? Here is code from :

private void backgroundWorker1_DoWork(object sender, DoWorkEventArgs e)
{
//Do Intensive Work
ArgumentClass backGroundCls = e.Argument as ArgumentClass;

       //Now you can do whatever you want to do with passed arguments

       int ctr=0;
       do
       {
           ctr++;
           backgroundWorker1.ReportProgress(ctr);
       } while (ctr < 10000000);

Favourite quote: In youth we learn, In age we understand.

But can we say that creating sqlconnection is unmanaged resource? This is even stated in Albhahari book too. I am still looking for clear answers.

Favourite quote: In youth we learn, In age we understand.

When we create database connection in C# lets say to SQl server, why it is recommended to use connection statements within using? I know using makes CLR reclaims memory when control is coming outside of using by calling Dispose(). But SQL server connection should be a managed code and using is usually used for unmanaged code. I mean we create SQL Server connection objects from .NET libraries, so why is unmanaged? Really looking for answer.

Favourite quote: In youth we learn, In age we understand.

Judah, Thanks for the nice solution. I have further question in your solution and it may sound stupid but help me. When I am using interfaces on client side how the call reaches to particular piece on server where this interface is implemented. I mean to say that this interface may have been implemented in different different areas. I know that to reach particular piece we do registration of server and give right address (tcp/http) on client side but my question is interface is just an abstract thing. How the call from client actually reaches to server. Please help.. Favourite quote: In youth we learn, In age we understand.

Hi, I have DotNet remoting question and this is related to while development. I am working on C#/windows application. One of client (window form) need to access the method remotely (from remoting server)...Question: When I am building the client while in development mode do I have to set reference explicitly to the DLL server (remotable object) because if I do that then when moving to production, I don't know in which folder remote server .DLL would be installed. Favourite quote: In youth we learn, In age we understand.

Hi, I have DotNet remoting question and this is related to while development. I am working on C#/windows application. One of client (window form) need to access the method remotely (from remoting server)...Question: When I am building the client while in development mode do I have to set reference explicitly to the DLL server (remotable object) because if I do that then when moving to production, I don't know in which folder remote server .DLL would be installed. Favourite quote: In youth we learn, In age we understand.