Update or configure an existing Service Reference in SL application you get duplicate Binding and Endpoint information. - by dsandor

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 505636 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/29/2009 7:26:10 AM
Access Restriction Public

Description

I am developing a silverlight application that is using a WCF service in my local solution. When I right click on the service reference in the SL application and choose update or if I click configure a duplicate Endpoint and Bindings for the service in my ServiceReferences.ClientConfig file:

     <endpoint address="http://localhost:15153/AdminService.svc" binding="basicHttpBinding"
        bindingConfiguration="BasicHttpBinding_IAdminService" contract="Proxy.AdminService.IAdminService"
        name="BasicHttpBinding_IAdminService" />
     <endpoint address="http://localhost:15153/AdminService.svc" binding="basicHttpBinding"
        bindingConfiguration="BasicHttpBinding_IAdminService1" contract="Proxy.AdminService.IAdminService"
        name="BasicHttpBinding_IAdminService1" /> 
Sign in to post a comment.
Posted by Microsoft on 11/16/2009 at 2:52 PM
Dear Customer,

Thanks for reporting the issue.
This issue has been resolved in the latest version of Visual Studio 2010.
Thanks!

John chen (Visual Studio)
Posted by Microsoft on 11/2/2009 at 11:24 AM
Hello,

If the user is renaming bindingConfiguration and endpoint name only. Visual Studio should not duplicate the configuration.

Is it possible for us to take a look at the complete ServiceReferences.ClientConfig file? In order to diagnose this properly; we need to find out what changed before "Update Service Reference".

Thanks
tobs
Posted by Microsoft on 10/30/2009 at 5:51 AM
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/30/2009 at 2:12 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team