This post originated from an RSS feed registered with Agile Buzz by James Robertson. Original Post: .NET Events and the .NET Connect Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general. Latest Agile Buzz Posts Latest Agile Buzz Posts by James Robertson Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Don't know about outgoing events (calling events from Smalltalk). But registering for events in .NET was not part of the version 1 plan. It is extremely difficult and there is no solution whatsoever at the moment (AFAIK for any *-.NET bridge).

The problem is that you need to give .NET a delegate object to call (type safe callback) and that has to be part of the managed world. We are thinking about synthesizing such objects (their classes) and having an extra callback mechanism with dedicated marshaling and ...

Calling the .NET-connect useless because of missing events is a result of an expectation mismatch. Events are heavily used in the UI part but rarely in the domain layer. Same as with Smalltalk. So at the moment we can use external domain functionality but embedding UI components is a different story altogether. Even with Event support today, we still have no concept for the emulated Windows.Forms widgets. These need a special wrapper environment that we very likely have to synthesize as well. For each Windows.Forms subform in an application. You get the picture.

.NET Events will be supported, but I'd rather not commit to a date until the engineers have had a better look