VS2008 creates a 2nd endpoint when actualising a web reference

VS2008 creates a 2nd endpoint when actualising a web reference

Hello out there,

I changed an existing and good working webservice from an wsHttpBinding 
to an NetTcpBinding.
This is working (after trying some time) and has real a better performance!

But one thing is strange: when I'm now actualising the web reference 
from within VS2008, VS2008
creates a 2nd endpoint config in my app.conf.
The endpoint is exactly the same as the existing but the name and 
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

          <identity>
            <userPrincipalName value="Domain\Username" />
          </identity>

Where Domain\Username is my username in the domain.
The client does not run with these informations, I have to remove them 
manually.


What's wrong with VS2008?


Thank you,
Frank

date: Wed, 23 Jul 2008 19:52:42 +0200 author: Frank Hauptlorenz am

RE: VS2008 creates a 2nd endpoint when actualising a web reference

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Frank,
\par 
\par From your description, you are developing an WCF service and a client through VS 2008. The service used to use wshttpbinding, and when you switch it to netTcpBinding and regenerate the service reference at client, you found the client generate two configuration section for the service endpoint , correct?
\par 
\par Based on my experience, such behavior might occur at the following situation:
\par 
\par * you have an WCF service endpoint using certain configuration(binding and behavior ...)
\par 
\par * you change its binding or other settings
\par 
\par * without remove the original client service reference(proxy class) in client project, you directly update the reference, it might keep the original reference setting and generate a new client endpoint entry.  
\par 
\par Therefore for this issue, I suggest you always first remove the existing client-side service reference(in solution explorer), this will make the IDE remove the proxy class and also clear the app.config file.  Then, add the "service reference" again in the project.
\par 
\par For the second issue you mentioned:
\par 
\par =====================
\par but the name and 
\par bindingConfiguration have the suffix "1" . Additional VS2008
\par creates this entry:
\par 
\par           <identity>
\par             <userPrincipalName value="Domain\\Username" />
\par           </identity>
\par =========================
\par 
\par based on the document you can see that this element <identity> is used to set a predefined identiy for the expected server-side service(not for client):
\par 
\par #<identity>
\par http://msdn.microsoft.com/en-us/library/ms731721.aspx
\par 
\par Therefore, it is generated by the IDE according to the server-side service's identity. By default when using netTCPBinding, WCF service endpoint will use windows authentication and if you are using the VS IDE test server(instead of IIS), the service's running process identity is the current logon user(that should be the "domain\\username" for your case.  You can manually specify another expected identity(but the default one is ok). 
\par 
\par Or if you do not need security feature for the current case, you can turn it off in your service configuration( in the NetTcpBinding configuration):
\par 
\par For example:
\par ==============================
\par   <system.serviceModel>
\par         
\par         <services>
\par             <service behaviorConfiguration="WCFIDESvr.TestServiceBehavior"
\par .............
\par               
\par                 <endpoint address="net.Tcp://localhost:8989/TestService" 
\par                           binding="netTcpBinding"
\par                           bindingConfiguration="TSBinding"
\par                           contract="WCFIDESvr.ITestService">
\par                   </endpoint>
\par              
\par ......................
\par             </service>
\par         </services>
\par 
\par       <bindings>
\par         <netTcpBinding>
\par           <binding name="TSBinding" >
\par             <!--  i  turn off the security here -->
\par             <security mode="None" >
\par               <transport clientCredentialType="None"/>
\par               <message clientCredentialType="None"/>
\par             </security>
\par                
\par           </binding>
\par         </netTcpBinding>
\par       </bindings>
\par       ================================
\par 
\par You can get more about the WCF configuration schema info here:
\par 
\par #Windows Communication Foundation Configuration Schema
\par http://msdn.microsoft.com/en-us/library/ms731734.aspx
\par 
\par and for WCF security programming:
\par 
\par #Windows Communication Foundation Security
\par http://msdn.microsoft.com/en-us/library/ms732362.aspx
\par 
\par If there is anything unclear, please feel free to post here.
\par 
\par Sincerely,
\par 
\par Steven Cheng
\par 
\par Microsoft MSDN Online Support Lead
\par 
\par 
\par Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@microsoft.com.
\par 
\par ==================================================
\par Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notifications.
\par 
\par Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support 
\par Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support 
\par professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations 
\par that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx.
\par ==================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par 
\par 
\par \pard\li720 --------------------
\par Date: Wed, 23 Jul 2008 19:52:42 +0200
\par From: Frank Hauptlorenz <ecstasy.tribe@nospam.nospam>
\par User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
\par MIME-Version: 1.0
\par Subject: VS2008 creates a 2nd endpoint when actualising a web reference
\par 
\par Hello out there,
\par 
\par I changed an existing and good working webservice from an wsHttpBinding 
\par to an NetTcpBinding.
\par This is working (after trying some time) and has real a better performance!
\par 
\par But one thing is strange: when I'm now actualising the web reference 
\par from within VS2008, VS2008
\par creates a 2nd endpoint config in my app.conf.
\par The endpoint is exactly the same as the existing but the name and 
\par bindingConfiguration have the suffix "1" . Additional VS2008
\par creates this entry:
\par 
\par           <identity>
\par             <userPrincipalName value="Domain\\Username" />
\par           </identity>
\par 
\par Where Domain\\Username is my username in the domain.
\par The client does not run with these informations, I have to remove them 
\par manually.
\par 
\par 
\par What's wrong with VS2008?
\par 
\par 
\par Thank you,
\par Frank
\par 
\par \pard 
\par 
\par }

date: Thu, 24 Jul 2008 03:22:18 GMT author: (Steven Cheng [MSFT])