I added a new attribute to the SharpToolbox: [BuiltForMono].
If you know development tools or libraries that are built for Mono or compatible with Mono, let me know. I would add them to the list. If they are already in the list, I'd do the necessary fixing to add the new attribute.
Today only a few tools are flagged as Mono compatible.
I was playing with services and containers, as part of my implementation of Inversion of Control. All was fine until events came into play.
I needed to connect two services through events. Oh, all was working fine: there were no apparent troubles. But under the too calm surface sneaked a dreadful memory leak. Events don't play well with a loosely coupled environment by default. Better be warned.
Dear Microsoft, we really need a date for .NET 2.0's "Go Live" license (and consequentely the beta 2). We need to know right now whether we should start developing with .NET 2.0 or whether it's too soon because we won't be allowed to deploy in production before next year or so.
If we don't have a date, there is no other option but keep developing new projects with 1.1 because we can't afford to postpone project releases. And that's bad because we'll have to recreate things that are in .NET 2.0, and dump a lot of code when .NET 2.0 is out.
So, please tell me, should I forget about .NET 2.0 right now, and not expect a "Go Live" license before December, November or so?
Clemens Vasters' post "Rows and Columns + Elements and Attributes is all you need" initiated an interesting discussion about the place of objects in SOA.
In my opinion, the way to work with Entities, Managers, Objects and Services is still not clear. I haven't looked enough at architectures like ShadowFax or FABRIQ to know whether they contain guidance on this. My guess is that we'll have to wait some more time before best practices become clearly defined. Maybe all this is already well settled in the J2EE world?
I tend to do something similar to what Udi does. One of the open issues I see is "how to share business and validation rules between the Business layer and the Presentation layer?". If the rules are in the Managers, and not in the Entities, how do we use these rules in the Presentation layer?
Anyway, "encore un pavé dans la mare des tout-objet"...
Keeping a link to the Visual Studio 2005 and .NET 2.0 beta documentation might be handy...
Les inscriptions sont ouvertes, et le nombre de places et limité. Qu'on se le dise...
Rendez-vous en octobre.
The lifecycle of Application, Page and Control in ASP.NET 2.0 is something you'll have to know and understand sooner or later. It is essential to put things where they belong, and this kind of information is not only for control writers. Jeff did a great work collecting it. If you want to learn about this lifecycle in ASP.NET 1.1 instead, you can visit this page.
I now have two CD ISO files to play with. Three to go to have the complete set...
Now I can't wait for... beta 2 and the "Go Live" license!