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

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

Closed

as External Help for as External

Type:	Bug
ID:	505636
Opened:	10/29/2009 7:26:10 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

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" />

Details (expand)

English

Visual Studio 2010 Beta 2

Windows 7

English

Add a service reference to a local WCF service to a Silverlight application. Check the code in to TFS. Right click on Service Reference in VS2010B2 SL app. Choose Update or Configure. The existing entries for the service contract should be updated and they are no, they are duplicated.

The existing entries for the service contract should be updated and they are no, they are duplicated.
Example:
<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" />

Should only update settings to the service bindings. VS 2008 worked correctly.

<endpoint address="http://localhost:15153/AdminService.svc" binding="basicHttpBinding"
bindingConfiguration="BasicHttpBinding_IAdminService" contract="Proxy.AdminService.IAdminService"
name="BasicHttpBinding_IAdminService" />

0 attachments

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

Posted by simeyla on 9/29/2010 at 9:53 PM

one workaround is to put the service agent (reference) in its own DLL and reference it from the main project.

it won't touch your service agent config in your web.config and you'll have a project with up to date serviceagent config if you ever need to compare it with what you have in web.config

also has the benefit that if you have one service agent referencing another it will share the types

MAIN DLL > ServiceAgent1 > ServiceAgent2

If ServiceAgent1 and ServiceAgent2 have shared types you won't get two generated classes