That will be :jig::jig::jig::jig::jig::jig::jig: etc... ~RaGE(); I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb

Are trying to be an echo? The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.

Programm3r wrote: link does not work You're right, that is one of the reasons it still is Work In Progress. However, the relevant stuff is in the article itself. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] I only read formatted code with indentation, so please use PRE tags for code snippets. I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).

Absolutely: ProcessCommunicator[^].

you are right, they should let you add an answer to your own question, and let you explicitly accept it. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Getting an article published on CodeProject now is hard and not sufficiently rewarded.

Hey. This problem has been bugging me a lot lately - Something really odd is happening in the framework. What's happening is the data field control is modifying the bindings on the control and re-setting them. Setting the SelectedItem works fine, but when it comes to re-set the ItemsSource property the binding for the *SelectedItem* property *vanishes* without a trace. The only workaround I have at the moment is to make the ItemsSource binding TwoWay, and ensuring that the property it's bound to is read-only. This stops the code from modifying the ItemsSource binding. However, I'm now finding that the bindings are disappearing under other circumstances as well (it looks like it's happening occasionally when there is more than 1 combo box in the form) - I haven't solved that one yet. Cheers, Mike

Strange - this is how I used it - ar = u.BeginInvoke(param, new AsyncCallback(Complete), "state"); ar.AsyncWaitHandle.WaitOne(); u was the my delegate and param was the parameter I passed into that method that my delegate invoked.

Well why should the message then read This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element. I do know about the cascading of config files - a great feature btw - but I do not know every detail about what can be configured in machine.config versus web.config/app.config, nor do I remember exactly how web services and WCF services are configured. In general however I have to say .NET usually does a fairly good job with error messages, compared to anything else I've used. That doesn't mean it's the right tradeoff tho! For every small improvement in the error reporting of any library used by many people, a lot of people can end up saving some time, and in aggregate quite a lot of time. That's the point I want to get across.

Thanks for the info Richard. The only programmers that are better C# programmers, are those who look like this -> :bob: :java: Programm3r My Blog: ^_^

Not sure. I haven't experienced this so far. All I can suggest is to try adding more timeout value. Navaneeth How to use google | Ask smart questions

Thanks for the information. I found this[^], which performs a keyboard hook. Kind regards, The only programmers that are better C# programmers, are those who look like this -> :bob: :java: Programm3r My Blog: ^_^

To solve issue buy and install the following Add-in-express[^] The only programmers that are better C# programmers, are those who look like this -> :bob: :java: Programm3r My Blog: ^_^

Ravi Mori wrote: You have to post this question in Linq Forum.. Your right ... sorry about that :sigh: The only programmers that are better C# programmers, are those who look like this -> :bob: :java: Programm3r My Blog: ^_^

Thanks firda, been looking for that code all over.

there is an error 'bmpImage.Clone(rec, bmpImage.PixelFormat);'. i think it might be 'bmpImage.size'<'rec.size', so bmpImage's memory < rec's memory ,and it caused the error .

Something like this works: private const int WM_ENTERSIZEMOVE = 0x0231; private const int WM_EXITSIZEMOVE = 0x0232; protected override void WndProc(ref Message m) { base.WndProc(ref m); switch (m.Msg) { case WM_ENTERSIZEMOVE: this.Opacity = 0.5; break; case WM_EXITSIZEMOVE: this.Opacity = 1.0; break; } this.Invalidate(); } Still trying to get rid of the small flicker.... The only programmers that are better C# programmers, are those who look like this -> :bob: :java: Programm3r My Blog: ^_^