Search
Resolved
as Fixed Help for as Fixed

0
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 491641
Opened: 9/23/2009 2:18:33 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I have a WCF service using basicHttpBinding, with an OperationContract that returns a string array. When I try to invoke it using a SoapHttpClientProtocol-derived proxy class in a .NET 2.0 client class, the WCF method is invoked and returns the array, but the proxy always gets an array with zero elements.

One possible workaround would be to add a web reference to the client app, but I'm trying to replace an old ASMX service with a new WCF version without changing the client application.
Details (expand)

Product Version

.NET Framework 3.5 SP1
Product Language
English

Operating System
Windows Vista RTM/SP1/SP2
Operating System Language
English

Architecture
x86

Priority
(1=blocking, 2=important, 3=nice to have)
1

Severity
(1=major functionality issue, 2=important functionality issue, 3=nice to have)
3

Steps to Reproduce
1. Create a WCF service that exposes an OperationContract that returns a string array. Bind using basicHttpBinding, host using WcfServiceHost.
2. Create a proxy class in a client app that derives from SoapHttpClientProtocol, and invokes the method exposed in the previous step.
Actual Results
The string array returned is always empty.
Expected Results
The string array should contain the values returned by the WCF method.
Component Usage
(any information on your scenario that may help in investigating your issue)
VS Team System 2008 Development Edition SP1 / .NET 3.5 SP1

How often does this happen?
Always Happens

Have you seen this problem in other versions?
I don't know if this issue existed previously
File Attachments
1 attachments
WcfStringArray.zip
Sign in to post a comment.
Posted by Microsoft on 9/24/2009 at 6:51 PM
Thanks for your feedback. We are routing this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 10/5/2009 at 5:31 PM
It looks like your question was answered on the MSDN forum at http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/62976c62-d88f-4589-a421-158e108bed3d/. If you need further assistance with this issue, please respond to this thread.
© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement