What's this? - Acropolis

Topics: CAB & Smart Client Software Factory
Jun 4, 2007 at 9:57 AM
http://www.microsoft.com/downloads/details.aspx?familyid=72386ce5-f206-4d5c-ab09-413b5f31f935
(via: Windows-Now.com)

Overview
“Acropolis” builds on the rich capabilities of Microsoft Windows and the .NET Framework, including Windows Presentation Foundation (WPF), by providing tools and pre-built components that help developers quickly assemble applications from loosely-coupled parts and services.

Would anyone like to comment, or has this been put on the web a bit early, and we'll have to wait for some sort of announcement?

Having not started with SCSF & CAB in earnest yet, should I be waiting for news?
Jun 5, 2007 at 3:24 AM
See the video here...

http://windowsclient.net/Acropolis/

I was wondering the same thing. What!! Yet another client framework from MS?

This is going to be immensly interesting and I need two more VMs!!!!
Jun 5, 2007 at 5:00 AM
Edited Jun 5, 2007 at 6:31 AM
Would definitely be interesting to hear anyone from P&P's comments on this - did they know about this, is it seen as complimentary or competing, or neither?

I noticed Brad Abram was blogging about it. He mentioned CAB on his blog but didn't go into much detail which. As he was involved in CAB originally I'm hoping he'll elaborate a bit more soon- http://blogs.msdn.com/brada/archive/2007/06/04/hello-acropolis.aspx

It appears to be very much CAB by numbers - instead of giving you a blank tableau and a framework to go and write a Composite UI, they are providing a very precise roadmap of how to implement composite UI solutions. It looks to be based on Services / commands, presumably events as-well, but I couldn't find any mention of ObjectBuilder.

Interesting.

Graeme

Jun 5, 2007 at 4:24 PM
I've seen Getting Started video and think that Acropolis is not based on CAB which is in SCSF. I suppose this is another framework totally targeted to WPF client applications and just built on the same architecture patterns. You see that Parts are derived from a base class, View and Part are associated using attributes to be found in run-time like TypeDescriptors.

But I like the idea of themes. I guess this is the right direction for shell skins or themes and something like injecting UIExtensibilitySites into the right place in a shell (shell theme).

So I think at this moment Acropolis could look brilliant in the comparison with SCSF only because of WPF UI :)

- Leonid
Jun 5, 2007 at 5:23 PM
From what i have been gathering from web postings and looking at the download (yes, i am yet to fire up my orcas VM and install it) it does not use SCSF or Enterprise Library. I could be wrong.

It appears that Acroppolis is using many of the new capabilities of .net3 and 3.5, like using Workflow for business rules and possibly navigation, wpf, etc etc..

Someone from P&P definitely should come out and tell us what their big plan for these two (obviously competing) frameworks and how and where the points of intersection would be.

-Salim
Jun 6, 2007 at 8:17 AM
I found this:
http://blogs.msdn.com/jaimer/archive/2007/06/04/acropolis-ctp1-released-to-web.aspx

Quote:

"Some of you might know Acropolis as an productization and WPF implementation of the Composite Application Block released by our Patterns & Practices team.. You are right, it is all that and a bag of chips... If you are a CAB user, no worries, the P&P team will release migration guidance to move to Acropolis. "
Jun 6, 2007 at 8:41 AM
Oh, and this forum thread on the Acropolis forum:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1690657&SiteID=1

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

Which references this:
http://blogs.msdn.com/dphill/archive/2007/06/05/introducing-acropolis.aspx

I've not read all that yet, but it looks like proper information is coming out, now.
Jun 6, 2007 at 11:41 AM
From the Glenn Block's post : "Acropolis takes the concepts of CAB to levels that folks in p&p might have never dreamed"

It's very interesting to know by the way what things guys in P&P have never dreamed? ;)

to P&P team: Any ideas? :)

- Leonid
Jun 6, 2007 at 3:46 PM
Personally I find this all very unsettling. Is CAB already "old"? Will it still be supported? Why is there no word from the P&P crowd? Anyone uneasy by this acropolis stuff??

:(
-Steve
Jun 6, 2007 at 5:11 PM
I can't say I am unhappy, but yes it is unsettling. It looks like Acropolis will likely have a different licensing. This is a wild guess since the project is not part of CodePlex that might not be the permissive or other kinds of relaxed licenses. Correct me if I am wrong. This is a bit disappointing. I am losing one more bet to my Linux friend.

This definitely changes, or atleast make us re-evaluate our plans of technology adoptions for our future development. I am sure that even without Acropolis it is a hard decision to make, not just in the MS ecosystem.

There definitely are some unresolved issues between P&P and the ".Net futures" crowd

-Salim
Jun 6, 2007 at 8:31 PM

sklett wrote:
Personally I find this all very unsettling. Is CAB already "old"? Will it still be supported? Why is there no word from the P&P crowd? Anyone uneasy by this acropolis stuff??

:(
-Steve


My thoughts coming in a blog post...
Jun 7, 2007 at 9:22 AM
Chris's post: http://www.chrisholmesonline.com/2007/06/06/acropolis/
Jul 12, 2007 at 8:59 AM
@Steve

SCSF / CAB will be supported regardless though we do not have any plans for future releases at this point. If you haven't checked it out, I urge you to look at the new SCSFContrib http://www.codeplex.com/scsfcontrib site. There you will find a full WPF implementation of CAB as well other goodies that the team has been working on.

@Leonid

Touche on the dreaming statement, what I meant with the comment was that product groups have far more resources to build products than we do in p&p. Not to say we would build the Acropolis designer even if we DID :)
Jul 12, 2007 at 9:01 AM
@Graeme

Acropolis is based on the same concepts that drive CAB, but not CAB itself. It does not use ObjectBuilder, etc. It does share concepts though like Views, Services, etc.