On a muse, i tried Clipboard.Clear();

That threw a threadstate exception telling me i had the wrong appt state.
This explains alot. I wish Clipboard.GetData() would throw an exception
instead of just returning null, it would have saved me half a day of beating
my head on my monitor. Since you cant change the appt state on a running
thread, and you cant create the thread that the remoting call comes in on,
your only option is to create another thread.



So here is what i did, it seems ugly to me, but works well even with alot of
calls from multiple clients. I'm sure i could improve it to have the other
thread loop, and a few other effiency things, but its not that important
where i'm using it.



1. lock (important because you never know everything when remoting is
involved)

2. create thread and SetAppartmentState

3. start thread

4. block until its done

5. get results, and return them (i used a property)



private Bitmap ReturnBMP = null;

private object BMPLock = new object();

private ManualResetEvent GetImageMRELock = new ManualResetEvent(false);

private Bitmap GetImage()

{

lock (this.BMPLock)

{

this.GetImageMRELock.Reset();

Thread t = new Thread(new ThreadStart(t_GetBMP));

t.SetApartmentState(ApartmentState.STA);

t.Start();

this.GetImageMRELock.WaitOne();

return this.ReturnBMP;

}

}



private void t_GetBMP()

{

IDataObject data = Clipboard.GetDataObject();

this.ReturnBMP = (System.Drawing.Bitmap)data.GetData(DataFormats.Bitmap);

this.GetImageMRELock.Set();

}



[quoted text, click to view]