PostSharp

[boonzaai]

Greetings,First of all let me compliment the people behind this great initiative! The first 'real' AOP(-ish) framework I found for .NET, so no disgusting containers or whatsoever  (e.g.Spring.NET).I am very eager to apply PostSharp in my professional projects, but that can only be done if some more light is shed on the roadmap. The software seems very high quality, but one of the more important aspects is the freezing date of the different interfaces - maybe a release date for the first beta or release candidate. In order to fit it in different planning stages,  I would also be very delighted to hear a projected date for a final first release.Thank you very much in advance. Keep up the good work, I'll be spreading the word GreetingsAndré

[gfraiteur]

Interfaces are really close to be frozen. A matter of weeks. Maximally one months. In fact, the only interfaces in which I plan minor changes are maybe Laos. But since PostSharp is developed in spare time, I cannot commit dates.
If no major problem is discovered after the release of Alpha 1, the interfaces should be committed to be forward compatible. However, if I receive feedback [url=/projects/postsharp/issue-tracker/19]of this type[/url], I will be forced to do breaking changes. Anyway, I will discuss them with people who have shown interest.
The low-level interfaces (not Laos) are used by two commercial companies, Starcounter (a company with no web!) and X-Tensive for DataObjects .NET v4.0 ([url=http://www.x-tensive.com/PressCenter/News/2007.01.08.htm]CTP planned for Q2 2007[/url]). I consider (and these partners also) that low-level interfaces are very mature.Hope this helped.

[gfraiteur]

After this conversation with Andre,  have decided to delay the 'frozen' milestone of PostSharp Laos to Beta 2. Beta 1 should still be frozen for other APIes, unless a major problem is discovered. More in [url=http://postsharp.blogspot.com/2007/01/laos-to-new-design-cycle.html]this blog entry[/url].