Current Scenario: I have a long running application that gets a job list from sql, creates a child process for each request and exchange status data with those child process with a full-duplex communication. All processes runs on the same machine as the host application, currently all processes are Win32 and I use WM_COPYDATA. Future: It is likely that in the next future the Win32 application will be rewritten to .NET, child processes will remain untouched, new child processes will be written in any language/platform (.NET, Win32) depending on 3rd party specifications/libraries. Question: I would like to hear some rant on how to implement interprocess communication between .NET and Win32 application. TIA

---( carlop )--- web @ www.carlop.com blog @ carlop-dev.blogspot.com

Probably you're victim of a well planned trick

---( carlop )--- web @ www.carlop.com blog @ carlop-dev.blogspot.com

Hi folks My doctor has told me that I have a problem on my right wrist... well I bet you know what... Carpal Tunnel Syndrome, a classic ! I've moved my mouse to the left hand and, after a couple of weeks of training, works fine for the moment. But I'm trying to figure out how to definitively avoid the mouse, so I'd like to hear from you if you can share your suggestions, experiences on alternatives devices such as - Trackballs - External touchpads or keyboards with integrated touchpad - Tablets such as the Wacom Bamboo - Macro-keys keyboards such as the logitech G11 - Any other device or keyboard you've used - Software that may help in reducing mouse or keyboard usage Thanks for sharing.

---( carlop )--- web @ www.carlop.com blog @ carlop-dev.blogspot.com

It was only an example. You don't use foreach but probably the problem is that while DataBind() method enumerates over the TestCollection another piece of code (maybe the same but from another thread) is doing the same. So try to lock the code that acess TestCollection before use it: lock (TestCollection) { ddlTest.DataSource= TestCollection; ddlTest.DataBind(); } paco

Is not allowed to modify any item of a collection in any way while you're inside the foreach loop on that collection. You may try to lock the piece of code, something like the following lock(this) { ... } paco

"Applied Microsoft .NET Framework programming" by Jeffrey Richter is a very good book that deepely covers both the framework and the CLR from a general point of view (strings, events, assemblies, GAC, Garbage collector, ..), it uses C# and IL to show some code snippet, there's nothing about windows forms, XML, ADO.NET and so on. paco