Array vs List for interoperability purposes with WCF

I have taken up a WCF project which has the convention of returning data in Arrays as opposed to Lists. I was told that the reason for this is to improve potential interoperability with non .NET consuming applications.

Are there any good examples that illustrate that it is worth returning Arrays from a WCF service instead of Lists?


I previously worked on a project with the same implementation, and the same reasoning. I was unable to get a valid explanation from any of the project team.

I'd like to hear a justification, but until I do I don't believe this.

Both Array and a List serialize as a collection in XML or JSON - there is no difference, because these are interoperable and functionally null languages. Note that when you use the 'Add Service Reference...' tool in Visual Studio, you have the option of using a List or an Array as your collection type.

If you use a binary serialization in WCF then there will be a difference between List and Array, but binary serialization only works from .NET to .NET so there is no potential for interoperability issues.

Need Your Help

What are the fields that the user table should contain from the security/authenication perspective?

sql-server database security authentication

When designing user table what would be the must have fields from the security/user authentication point of view for a Web based Application (.NET and SqlServer 2005)

Delphi: OpenFileDialog crashes with URL

delphi url uri openfiledialog

Giving a URL to the TOpenFileDialog, the Execute method throws an exception: