So it was the "Acropolis". should replace the product and the fact CAB (Composite UI Application Block) ...
Here's the official announcement:
Acropolis team blog
The findings from the Acropolis project to be dismembered and fed into the . NET class library (version 4.0). This hypothesis I have already referred to the BASTA! expressed in 2007 in Mainz, where I gave a talk on CAB and showed a view of Acropolis. An article for the dotnet magazine was already in the works. But an inner voice has retained me to keep going. Now I know why!
On behalf of the CAB community, it rained a lot of criticism of Acropolis. The trouble was that the CAB and Smart Client Software Factory no longer be developed. Instead, the ambitious project Acropolis raised that much wanted but could not. The biggest problem was a non-existent roadmap for the product.
Here is a commentary from the cabinet Comunity. Requiem for Acropolis; Fanfare for CAB +
But there is yet another new project: WPF Composite Client
This time, again under the direction of the Patterns & Practices Group. Here, the whole experience of CAB flows with a. Acropolis is (was) Namely, a project of UIFX team that is responsible for ASP.NET and WPF.
Glen Block bescheibt in his blog the new project.
Glenn Block
WPF Composite Client is not a new version of CAB. There will be a new library and guidance. Target platform is WPF. The reason for building a new class library consists that CAB was not designed for WPF. WPF brings its own concepts such as Command and RoutedEvents with it, it is not in WinForms and therefore are not supported in CAB.
WPF also offers a completely different "experience". It will therefore be no
migration path from WinForms. (Just as it was scheduled by the Acropolis).
How sounded out pass it on improvements to WinForms! WinForms is therefore not yet retired.
I first let the corks pop, the issue that we can Acropolis behind us! I have fears that we have to deal seriously with the product!
My
0 comments:
Post a Comment