We are trying to get a handle on how activity data is treated in the future authoring tool. Will the package manifest hold all activity data or will each activity have its own activity data file? We really like the idea of populated activities being autonomous and shareable in whatever architectural treatment can achieve that.
By design, the manifest describes the data that is associated with each Activity, and can be used to include data that is amenable to XML representation (and relatively short - there is an 8k limit on strings I think). For non-trivial amounts of data such as unbounded xml documents, images, video or custom binary data, libraries are available and recommended.
The Authoring tool will support these design principles. Can you elaborate on your specific ideas/concerns here? Your question is quite general.
Terms of Use | Code of Conduct | Privacy Statement | Trademarks | © Microsoft 2010