Windows Forms

using System;
using System.Windows.Forms;

namespace LP_Core {
    public class LP_WaitCursor : IDisposable {
        private Form form;
        public LP_WaitCursor(Form form) {
            this.form=form;
            form.Cursor=Cursors.WaitCursor;
        }
        public void Dispose() {
            form.Cursor=Cursors.Default;
        }
    }
}

string temp = someObject.SomeValue;
someObject.SomeValue = "Updating, call again later";
try
{
    // do stuff
}
finally
{
    someObject.SomeValue = temp;
}

Bastard Programmer from Hell

Eddy Vluggen wrote:

why use a Form over a Control?

Eddy Vluggen wrote:

an optional parameter to indicate whether to disable the control

Eddy Vluggen wrote:

LockWindowUpdate

Luc Pattyn wrote:

I considered that too, but I would probably never use it. Most apps have several ways to get something done (MainMenu.MenuItem, ContextMenu.MenuItem, Button, KeyDown), so there isn't just a single Control to disable, I often have a Command object that sits in between several Controls and a single Action, however that would make my WaitCursor too specialized IMO.

Luc Pattyn wrote:

Never used it. As it is bound to be a short operation, I probably would not care much. Longer operations, I'd do in a BGW, and I make sure the GUI updating is periodic rather than continuous.

Bastard Programmer from Hell

dcof wrote:

1. Do you know of a reference of that has a desktop form accessing the active
directory? The only one I know about is an asp.net applcation accessing the
active directory.

dcof wrote:

2. In this application, I would like the windows desktop application to pass the
authenication(active directory) information to sql server 2008 r2 by either user
or by group.

public string Whoami()
    {
      string str;
      int idx;
      str = System.Web.HttpContext.Current.Request.LogonUserIdentity.Name;
      idx = str.IndexOf("\\");
      return str.Substring(idx + 1);
    }