blocks|key|720544|text|MyClass是您为其添加了服务引用的服务使用的类吗？如果为true，则MyClass.cs中的每个类有两个版本:一个来自MyClass.cs，另一个来自服务引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|720545|你应该选择其中一个-要么使用服务，要么不使用服务。|720546|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Is MyClass a class used by the service for which you added a Service Reference? If true, then there are two versions of each class in MyClass.cs: one from MyClass.cs, and one from the service reference.

You should pick one or the other - either use the service or don't use the service.

blocks|key|2632573|text|如果您在Silverlight和Web项目中都添加了"MyClass.cs“作为链接，那么很可能会导致名称冲突，幸运的是，它们应该位于不同的名称空间中。链接的类将位于原始命名空间中，而由服务引用生成的类将位于生成的命名空间中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2632574|您可以在生成服务引用时使用"Reuse+Types+in+Reference+Assemblies“选项，以便生成的服务代理使用您的链接类，而不是生成新的类。然而，有几个技巧可以让它正确工作，我在几个月前的一篇文章Resuing+types+in+Silverlight+Service+References中概述了这些技巧。|offset|length|2632575|我希望这能帮到你。|2632576|entityMap|0|LINK|mutability|MUTABLE|url|http://compiledexperience.com/Blog/post/Resuing-types-in-Silverlight-Service-References.aspx^0|0|2Z|1B|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If you've added "MyClass.cs" as a link in both your Silverlight and Web projects then it will most likely cause a name collision, fortunately they should be in seperate namespaces. The linked class will be in the original namespace and the one generated by the Service Reference will be in the generated namespace.

You can use the "Reuse Types in Referenced Assemblies" option when generating the Service Reference so that the generated service proxy uses your linked class rather than generating a new one. There are however a couple of tricks to get this to work correctly, I outlined these in a post a few months ago <a href="http://compiledexperience.com/Blog/post/Resuing-types-in-Silverlight-Service-References.aspx" rel="nofollow noreferrer">Resuing types in Silverlight Service References</a>.

I hope this helps.

blocks|key|4034560|text|奈杰尔·桑普森的回答让我找到了正确的方向，非常感谢！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4034561|该解决方案为类文件创建一个新项目，并在您的Silverlight项目中添加对该项目的引用。然后，当您广告您的服务引用并选择“重用引用的程序集中的类型”时，它将不会生成它自己的类实现，从而消除了不明确的引用。|4034562|与典型的客户端/服务器服务场景不同，对于Siverlight和ASP.NET，类文件必须分别编译。|4034563|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Nigel Sampsons Answer led me in the right direction, thanks a million!

The Solution
Create a new project for the class file, and add a reference to that project in your Silverlight Project. Then when you ad your service reference and select "Reuse Types in Referenced Assemblies", it will not generate it's own implementation of the class, eliminating the ambiguous reference.

Unlike a typical client / server service scenario the class file must be compiled seperately for Siverlight and ASP.NET.

blocks|key|2632609|text|当我配置服务引用时，只需取消选中re=checking+"Reuse+types+in+reference+assemblies“，就可以克服这个问题。我得到了类库和服务引用之间的模棱两可的引用，这导致了我所说的级联错误，随着我所做的每一步都在增长。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2632610|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've been able to overcome this issue by simply un-checking the re=checking 
"Reuse types in referenced assemblies" when I configure the service reference. I was getting ambiguous references between the Class Library and the service reference which resulted in what I refer to as a cascade of errors, growing with every move I made.

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). 

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. 

Assumptions &amp; Clarifications 
I ensured that no namespaces, class names, methods or variables had similar names 
WCF service must reside in web application to have access to other non Silverlight assemblies etc 
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. 

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?

Ambiguous references with linked .CS File and WCF Service

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

为简洁起见，本文涉及Silverlight文件中的不明确引用，该文件的项目包含对Page.XAML.CS服务的服务引用和作为“链接”添加的MyClass.cs文件。该解决方案包含Silverlight项目和一个Web项目，该项目包含一个WCF服务和一个MyClass.cs文件(以及aspx文件等)。由于某些原因，一旦我...

问具有链接的.CS文件和WCF服务的不明确引用
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问具有链接的.CS文件和WCF服务的不明确引用EN