Inherited properties do not appear in soap sample on asmx file - by Grinn Daddy

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 520200 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/14/2009 7:33:53 AM
Access Restriction Public


I have two classes, WebServiceRequest and OrderRequest. Each class has properties. OrderRequest inherits from WebServiceRequest - like so:

    public class WebServiceRequest
        private string mAuthenticationToken;

        public string AuthenticationToken
                get { return mAuthenticationToken; }
                set { mAuthenticationToken = value; }

public class OrderRequest : WebServiceRequest

        private string mVendorId;
        public string VendorId
                get { return mVendorId; }
                set { mVendorId = value; }

OrderRequest is exposed via a WebMethod. When viewing the WSDL of the ASMX file that exposes OrderRequest (i.e. MyWebService.asmx?WSDL), both properties are visible - as they should be. These properties are also accessible when subscribing to the Web Service. However, when you view the SOAP Sample for the Web Method that exposes OrderRequest, only the VendorId property is visible, and not the inherited AuthenticationToken property. There does not appear to be any means of making the inherited properties visible in the SOAP Sample.
Sign in to post a comment.
Posted by Microsoft on 2/8/2010 at 11:58 AM
Sounds good.
Posted by Grinn Daddy on 1/12/2010 at 6:19 AM
I thought that might be the case, since ASMX Web Services are a bit outdated now. Since I discovered this bug, do I get to name it? If so, I want to call it the "Good Times Jelly Doughnut Denny Bug".
Posted by Microsoft on 1/11/2010 at 11:34 PM
We have confirmed that the inherited properties do not show up in SOAP Sample on the browser and that is indeed a bug in the product.

At this point, this area is in maintainance mode, and no active work is planned.

thank you for reporting it.
Posted by Grinn Daddy on 1/5/2010 at 6:53 AM
I've attached some sample code. In my sample, VendorId, TransactionId, and all the other *direct* properties of the OrderRequest object show up, but AuthenticationToken, the property OrderRequest inherits from WebServiceRequest, does not.

No, the issue you referenced is not what I'm referring to. This issue occurs when exposing one class that inherits from the other, either as a parameter of your WebMethod or as the return value. When you browse the ASMX file in your Web Browser, and click on the WebMethod (WebService.asmx?op=HelloWorld in my attached sample code), the above-mentioned AuthenticationToken property is not displayed in the sample SOAP requests.
Posted by Microsoft on 1/4/2010 at 11:42 PM
Thank you for submitting this issue.

Couple of questions
- Can you please provide the actual source & .asmx files?
- When you refer to the "SOAP Sample" - are you referring to the help page or a particular sample in the SDK?

Also, are you looking to do something similar to - ?

Posted by Microsoft on 12/15/2009 at 7:18 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(