Home/ Questions/Q 45575
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T15:49:51+00:00

I recently built an API and was often asked to replace the StringCollections I

  • 0

I recently built an API and was often asked to replace the StringCollections I was returning by objects containing a single property, The reason being that it was easier to bind with a listview or other controls in ASP.Net.

Since the API was used by the web application, the Web service and the dataloader I decided on keeping the StringCollection as my return type.

The methods returned labels for groups or report names.

Did I make the right choice? In such a situation how do you go about justifying your choice?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I don’t think you should make your API more complicated than needed just to satisfy the limitations a data binding module.

    But you could perhaps provide a wrapper class for a StringCollection that adapted it to the demands of the data binding module?

    Edit: This wrapper should be considered part of the data-binding layer rather than your data API, since it is something created specifically to adapt to the databinding module. It is irrelevant to other consumers of your data (if I understand your description correctly).

    • 0