title: Ambiguous references with linked .CS File and WCF Service
body: <p>For brevity purposes, this post relates to ambiguous references in a Silverlight Page.XAML.CS file, whose project contains a service reference to a WCF service and a MyClass.cs file added as a 'link'. The Solution contains the Silverlight Project and a Web Project that contains a WCF service and a MyClass.cs file (along with the aspx files etc).  </p>
  
  <p>For some reason I am getting ambiguous reference errors once I add the service reference to Page.xaml.cs.  Prior to adding the using statement for the service ref, I had one for MyClass.cs (which remember had been added to the SL project as a link) to the page, and it was running fine. Once the SVC ref is added, the compiler complains about ambiguity in my call to any class / property in 'MyClass.cs, such that a reference to MyClass.Class  becomes ambiguous to 'ServiceReference.MyClass.Class...Seems very strange to me. </p>
  
  <p>Assumptions &amp; Clarifications<br/><br/>
  I ensured that no namespaces, class names, methods or variables had similar names <br/>
  WCF service must reside in web application to have access to other non Silverlight assemblies etc<br/>
  Other .cs files in the Silverlight project reference MyClass.cs, otherwise I would have simply removed the link to MyClass.cs, and allowed referenced MyClass.cs through the service ref.<br/></p>
  
  <p>My assumption here is that this has something to do with adding a file as a link?  Any KungFu Masters out there able to offer some insight as to why this is occurring, alternatives to adding as a linked file, other ideas?</p>