Print Page | Close Window

[ANSWERED] Acropolis

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=529
Printed Date: 04-Jun-2024 at 11:54am


Topic: [ANSWERED] Acropolis
Posted By: Linguinut
Subject: [ANSWERED] Acropolis
Date Posted: 29-Oct-2007 at 11:08am
In a http://www.chrisholmesonline.com/2007/05/11/cab-solving-the-active-view-problem/#comment-11894 - comment on a Holmes blog entry:
 
"...with the announcement of Acropolis the P&P team is not going to be doing much more to CAB..."
 
I read this as CAB is not going to have another version.  Acropolis will be the next framework which incoroprates .NET 3.0+ functionality.
 
What affect does this have on DevForce Cabana project?  Or, the app that I am building with DF/CAB?


Replies:
Posted By: Linguinut
Date Posted: 29-Oct-2007 at 12:49pm

Interesting... http://blogs.msdn.com/gblock/archive/2007/06/06/acropolis-the-future-of-smart-client.aspx - http://blogs.msdn.com/gblock/archive/2007/06/06/acropolis-the-future-of-smart-client.aspx


Posted By: Bill Jensen
Date Posted: 30-Oct-2007 at 11:35am
Ward has posted his comments here:
 
  http://neverindoubtnet.blogspot.com/2007/10/requiem-for-acropolis-fanfare-for-cab.html - http://neverindoubtnet.blogspot.com/2007/10/requiem-for-acropolis-fanfare-for-cab.html
 
The gist of it is:
  • Acropolis has been mothballed - "the ideas will find their way into future versions of .NET"
  • This lifts the cloud that hung over the future of CAB; developers need no longer wonder "should I develop in CAB or wait for Acropolis?"
  • The Microsoft patterns & practices people (p & p) who gave us CAB are stepping into the breach. They are now carrying the MS banner for composite UI development.
  • CAB for WinForms lives!
  • There are two extant CAB variants for developing in WPF
    • SCSF 2007 allows you to drop WPF parts into a WinForms CAB application
    • WPFCAB is CAB translated to WPF - same CAB APIs but with WPF UI controls.
  • P & P is launching a new effort called WPF Composite Client (WPFCC) that will be rebuilt from the ground up with WPF firmly in view. It will abandon the CAB interfaces but it will carry forward the critical architectural elements.
  • I feel very good about the prospects for WPFCC and would expect a working version in one year to 18 months.
  • While there will be no way to migrate from CAB to WPFCC automatically, I think that the transition will be reasonable and certainly easier than if you tried to move from a standard .NET app to WPFCC.
  • Customers who have existing investments in CAB should be pleased because there is now money and attention for CAB development and there is a realistic prospect of a CAB successor.
  • Customers who were thinking about CAB but worried about Acropolis should consider developing in CAB for WinForms today. If they want to get into WPF, they should consider WPFCAB today.

Bill J.

Posted By: Linguinut
Date Posted: 30-Oct-2007 at 12:01pm
Thanks!  It's tough to keep up with this stuff, sometimes.
 
Also, see...
 
http://blogs.msdn.com/gblock/archive/2007/10/26/wpf-composite-client-guidance-it-s-coming.aspx - http://blogs.msdn.com/gblock/archive/2007/10/26/wpf-composite-client-guidance-it-s-coming.aspx

Posted By: Linguinut
Date Posted: 30-Oct-2007 at 12:44pm
Great article by Ward, btw.  Thanks a ton!


Print Page | Close Window