Hi Brian,

How many services and controllers is really up to your what you are trying to accomplish and what is the best design for that.  There is no single answer to this.

For example, you could have a a single controller mapping to a single service and in that service multiple DataWindows are used.  As another example, you could have a single controller mapping to multiple services and in each of those services multiple DataWindows are used.

The templates in SnapDevelop for scaffolding the controllers and services are based on repository pattern of programming.  But you can create your own templates so SnapDevelop scaffolds your project the way you want.

Just to clarify, you will have a C# model for each DataWindow.  So 100 DataWindows means 100 C# models.  The C# model is basically the C# flavor of the DataWindow data object that is the definitions of the DataWindow.

Best regards,
Armeen

Looking for an example of what you said above "you could have a a single controller mapping to a single service and in that service multiple DataWindows are used".  As I mentioned above, I have a sample app I built with 2 dws which retrieve from 2 different tables.  No retrieval arguments, nothing fancy, just basic retrieve the contents of the table.

In DepartmentService.cs I have the following:

I have the exact same thing in EmployeesService, except all the references to <Department> are replaced with  <Employees>.  In order to use a single service, do I still need 2 retrieve methods defined:

public async Task<IDataStore<Department>> RetrieveAsync(CancellationToken cancellationToken)

public async Task<IDataStore<Employees>> RetrieveAsync(CancellationToken cancellationToken)

Or can I can a create a generic Retrieve which will take any dw passed in (not specifically Department or Employees)?

Thanks again for your help!

Brian

Hi Brian,

Yes, you can have a single service which would retrieve all the DataWindows. You would just pass in the name of the DW and any parameters the DW might require. There is, in fact, a demo application that uses this technique (https://github.com/Appeon/.NET-DataStore-Example). It also includes a PB client demo app so that you can see how to consume the Web API.

public IDataStore Retrieve(string dataobject, params object[] keyValue)
{
   var datastore = new DataStore(dataobject, _context);

   datastore.Retrieve(keyValue);

   return datastore;
]

Regards,