Databases
StackOverflow2013
Postsdbo
POWhy is WCF generating a different proxy?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy is WCF generating a different proxy?
    primarykey
    data
    text
    <p>I am adding a Service Reference to a Peoplesoft WSDL. The existing app has a proxy that was generated in a different version of .NET (4.0 I think) or svcutil. The old proxy starts like this:</p> <pre><code>//------------------------------------------------------------------------------ // &lt;auto-generated&gt; // This code was generated by a tool. // Runtime Version:4.0.30319.235 // // Changes to this file may cause incorrect behavior and will be lost if // the code is regenerated. // &lt;/auto-generated&gt; //------------------------------------------------------------------------------ namespace PeopleSoft.CustomerService { using System.Runtime.Serialization; using System; [System.Diagnostics.DebuggerStepThroughAttribute()] [System.CodeDom.Compiler.GeneratedCodeAttribute("System.Runtime.Serialization", "4.0.0.0")] [System.Runtime.Serialization.CollectionDataContractAttribute(Name="CIFaultTypeShape", Namespace="http://xmlns.oracle.com/Enterprise/FSCM/schema/M866879.V1", ItemName="IBResponse")] [System.SerializableAttribute()] </code></pre> <p>But the new proxy looks like this:</p> <pre><code>//------------------------------------------------------------------------------ // &lt;auto-generated&gt; // This code was generated by a tool. // Runtime Version:4.0.30319.239 // // Changes to this file may cause incorrect behavior and will be lost if // the code is regenerated. // &lt;/auto-generated&gt; //------------------------------------------------------------------------------ namespace Tasks.Services.ServiceReference1 { /// &lt;remarks/&gt; [System.CodeDom.Compiler.GeneratedCodeAttribute("System.Xml", "4.0.30319.233")] [System.SerializableAttribute()] [System.Diagnostics.DebuggerStepThroughAttribute()] [System.ComponentModel.DesignerCategoryAttribute("code")] [System.Xml.Serialization.XmlTypeAttribute(Namespace="http://xmlns.oracle.com/Enterprise/FSCM/schema/M866879.V1")] </code></pre> <p>Clearly the same WSDL is resulted in different proxy classes. We have old code that relies on a FaultType (<code>CIFaultTypeShape</code>) that doesn't get generated in to the proxy class. </p> <p>Is this a WCF issue that is causing that FaultType to be ignored?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsebagomez
    1. USKevin Raffay
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy is WCF generating a different proxy?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan it be that the first proxy is generated using svcutil.exe and the second one using Add Service Reference from Visual Studio? The problem might lie in a different serializer (Xml vs DataContract) being used.
      singulars
      1. POWhy is WCF generating a different proxy?
      1. USCodeCaster
    2. COThanks, but we traced it down to a VS 2010 bug.
      singulars
      1. POWhy is WCF generating a different proxy?
      1. USKevin Raffay
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload