On-demand discovery

Large applications can be broken into smaller modules, downloaded "on demand".  In Silverlight applications, Visual Studio tooling allows the developer to create separate deployment packages which can be dynamically downloaded as needed.  Non-Silverlight applications can also download additional assemblies as needed.  

To use DevForce within a downloaded module you must register it for on-demand discovery.
Unknown macro: IBNoteThe "IBNote" macro is not in the list of registered macros. Verify the spelling or contact your administrator.

Overview

On-demand discovery allows DevForce to probe your new content for any entity models, known types, or custom implementations of DevForce types.

You can ask DevForce to download the content, or once downloaded you can tell DevForce about it. Adding dynamic content for on-demand discovery causes DevForce to recompose its "parts" catalog and metadata about your models and components. If you have dynamic content which you neglect to tell DevForce about, you'll find both that your customizations are not found and exceptions occur when using the entity model. (The most likely error is a message that the entity type queried is not a "known type".)

You can register new modules at any time, and start using your entity model and other DevForce features within it as soon as discovery completes.  The CompositionHost  will fire a Recomposed event once ready, which you can listen on to check for completion or if any errors occurred.

To perform on-demand discovery, use one of the CompositionHost.Add overloads. Trace messages are also generated, which you can capture using a custom logger or trace viewer.  

In Silverlight

It's common practice to use Application Library Caching (ALC) for XAPs in a multi-module application. The DevForce assemblies all support ALC.  

You can add dynamic content to a Silverlight application in several ways.

With Cocktail

If you're using Cocktail, it has built-in support for on-demand loading and discovery.  Use the Composition.AddXap method to add dynamic content to your application.  See here for more information and sample code.

With Prism modularity

If you're using Prism modularity you can tell DevForce about the new content, either once the module downloads or when it initializes.  Here's a sample which adds the Uri of the downloaded module to the CompositionHost.   

See our sample DevForce/Prism Modularity Quickstart for more information.

With MEF deployment catalog

If you're using the MEF DeploymentCatalog, once the catalog downloads you can tell DevForce that new content is available by adding the DeploymentCatalog to the CompositionHost.  For example:

If using the DeploymentCatalogService shown in MEF samples, you likely already have code for the catalog_DownloadCompleted event handler. Add the line to call CompositionHost.Add for the catalog.

With a DynamicXap

If you're not using Cocktail, MEF or Prism there's still another means of notifying DevForce about dynamic content with the DynamicXap class.  The class can be constructed in a few different ways, but the easiest may be with a Uri, to have DevForce automatically download the content.

Listening for DynamicXap load

You can load a DynamicXap without adding it to the CompositionHost.  Listen on its Loaded event to tell you when the download has completed or if an error occurred.

In .NET

Dynamic content can be added to standard .NET applications too.  

Use CompositionHost.Add(catalog) to add either an AssemblyCatalog or AggregateCatalog to the MEF composition container managed by DevForce.

Listening for recomposition events

Regardless of how you've added content to the CompositionHost, you can listen for its Recomposed event to notify you when new content has been downloaded.

The RecomposedEventArgs will indicate the Xap or assembly triggering the recomposition, or the error if an exception was thrown.  You can use the Name property on the Xap to identify the on-demand module.