Use/generate methods signatures with int[] insted of ArrayOfInt on .NET web service

Question

I have a ASP.NET web service (.asmx) with methods that receives int arrays (int[]) and nullable int arrays (int?[]) as parameters. I also have a test web application for consuming this web service via a Service Reference.

The problem is that every time I change something in the web service code, recompile it and update the service reference at the test application, a different type of parameter is generated for the web service methods on the test application. For example:

On the first build and service update, the method signature generated by Visual Studio at the test app is:

void MyMethod(int[] firstParam, int?[] secondParam).

Then I make some changes, do it again and get something like:

void MyMethod(ArrayOfInt fistParam, ArrayOfInt1 secondParam)

(with ArrayOfInt being the equivalent of int[] and ArrayOfInt1 being the equivalent of int?[]).

Once more, and I get:

void MyMethod(ArrayOfInt1 firstParam, ArrayOfInt secondParam),

with ArrayOfInt and ArrayOfInt1 swaped (ArrayOfInt1 being now the equivalent of int[] and ArrayOfInt being the equivalent of int?[]).

What I really want is to use the simple int[] and int?[] types (no matter how many times I recompile and update the service reference!). How can I achieve this?

Answer 1

Try using wsdl.exe tool to generate web service proxy instead using Visual Studio.

This work for me!

Answer 2

I know this is old, but I just ran across the same issue. The difference for me was adding a web reference rather than a service reference.

Within VS, perform the following:

1. Right-click, select Add > Service Reference
2. Click the Advanced button in the lower left
3. Click the Add Web Reference button in the lower left
4. Add the URL and reference name then click Add Reference

My web reference properly added the method with int[] parameter.

EDIT: Here is a better answer with pretty pictures to illustrate!

EDIT 2: This answer gets rid of the ArrayOfXXX to List<XXX> silliness and doesn't use the legacy tech, so win-win as far as I am concerned. Now, how to do this within the tooling? Or is it only something you can do by editing the file directly?