Will acropolis have an update management system to update parts?
Or are the parts more of a build type connection?
Kind of a vailed attempt to ask if this will have a plugin system similar to Eclipse with 'dynamic updates' or are applications simply built by combining parts 'staticly' and depend on installs to update the whole app.
Can parts be reused over multiple apps and again what's the versioning strategy there?
The versioning strategy is one of the interesing points.
Since the problems of hosting 1.1 assemblies in .net 2.0.
I 've 'nt seen any promise of microsoft of reusing 'old' assemblies in new .net versions.
I hope acropolis can handle with these problems better.
So an answer will be very helpful
I just posted a reply to a related question about the use of System.AddIn within Acropolis to provide isolation and versioning support which I think is relevant to this question too. System.AddIn provides a very general and robust mechanism to address a lot of the issues you describe and we are working on integrating it into Acropolis so we can take full advantage of it.
Also, to answer your other question, Acropolis will indeed support both static (design-time) composition as well as dynamic (run-time) composition in the manner that you suggest (including the ability to dynamically load or unload components that are updated while the application is running - again thanks to System.AddIn features).
We don't have System.AddIn integrated yet unfortunately. We are working on it now and hopefully will have it integrated in a CTP release soon.