Bug with Service/Business Objects
-
It seems that there's a bug in Visual Studio with reference to updating service references where the service contains an object(s) with the same name as an object(s) in another reference already in the project. For instance, let's say you have a reference to a "Business" project that contains an object called "Customer", in the namespace "Business". You also have a Service with an object called "Customer" in the namespace "Service". When you add/update your service reference Visual Studio seems to create a whole bunch of problems. The only solution we've found in the application we're developing is to delete the "Business" reference before adding/updating the service reference and then adding the "Business" reference back into the project. We've spoke to Microsoft about this particular issue and they told us to change our object names. Seems like a pitiful solution to me. Rather it seems like they should fix the bug. There's no reason objects in separate namespaces should conflict. Any thoughts?