Data Access Pattern implementation for Composite Application

Nov 25, 2009 at 9:47 AM

Is there a recommended pattern in prism context for data access or is there a refference implementation sample for data access.

For example:

I am using which is not directly compateble with linq.

I will implement my Data Access Objects and business object (models)

I am using view, presentationModel, Controller, Service sequence

Where should be my Data access objects in another module or in infrastructure project or else where?

Is there convention, standard, guidance in prism or Composite application wpf framework?


Nov 25, 2009 at 2:31 PM


Prism does not provide any guidance on how to implement data access functionality for your application. Where to place your data access objects really depends on whether they are shared across modules or their functionality is specific to a particular one. For example, if you have a single service that will be used by all modules, registering it in the container as a singleton could be a good approach. In this case it wouldn’t matter if the service is in an Infrastructure project or in a module that loads all data access services.

You might find some useful information in the following links:

Please let me know if this helps.

Damian Schenkelman