-ursri

If you need dynamic forms I would write a dynamic form generator. Take a look at the Silverlight DataForm control. This generates a form at runtime.

Dynamic form generators are not that hard to write. They are typically created using some form of metadata. The richer the metadata, the better the generated code will be.

Example:

Property: FirstName
Tooltip: ….
Max Length: …

How the form gets generated has nothing to do with how it is consumed ih the UI.

Once you get your generator working, WPF is so cool that it makes databinding the generated form to a viewmodel an after thought (very easy to do).

Cheers,

Karl

Lets consider First name(txt), last name(txt), status(combo box), address(txt) are the controls in Candidate and Employee screens. Would it be good idea to store scree_name,screen_control,screen/control_displayname, and associated commands for both Candidate & Emplyee in database and call a generic view-BasicInfoView.xaml for both requirements, dynamically assign displayname & commands to controls? Does MEF address in same line?

Regards
ursri

Anything is possible. You may want to look at MEF for run-time discovery and loading of assemblies.

The question is, “is this necessary?” That usually depends on the application requirements.

This will make the application more complex unless the dynamic loading screens can work in isolation.

But this is possible and doable.

Cheers,

Karl