blocks|key|735852|text|我个人会从LINQ+to+Objects开始。你不需要任何购买-你可以在你的代码中使用LINQ，让他在他的代码中使用foreach循环，条件等……最终，他可能会注意到你的代码更具声明性，更清晰，更简短。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|735853|使用ORM普通ADO.NET的决定是一个更大的决定，而且这个决定的后果远远超出了LINQ语法。|735854|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|$]]

I would personally start with LINQ to Objects. You don't need any buy-in then - you can use LINQ in your code, let him use foreach loops, conditions etc in his code... and eventually he may notice that your code is more declarative, clearer and shorter.

The decision to use an ORM vs plain ADO.NET is a bigger one, IMO - and one with ramifications well beyond just LINQ syntax.

blocks|key|938979|text|LINQ很棒--但在引入其他技术时要小心，特别是当你的公司已经确定了一个标准的时候。对于开发人员来说，没有什么比支持100种不同的方式来做同样的事情更让开发人员恼火，也没有什么比支持成本更高的了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|938980|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|$]]

LINQ's great -- but use caution on introducing additional technologies, especially when your company has already settled on a standard. There is nothing more annoying to a developer and costly to a business than having to support 100 different ways of doing the same thing.

blocks|key|939006|text|我们在我工作的地方遇到了类似的问题。我的论点是，LINQ是一种一致的方式来查询任何支持IEnumerable+(和其他)的东西，而不仅仅是数据库。但是，当使用它来查询数据库时，您可以获得所有查询都是强类型的附加好处。在执行内联SQL或调用存储过程时，不会出现这种情况。当实体定义发生变化时，这种好处是巨大的。编译器将为您完成所有工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|939007|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|$]]

We're running into a similar issue at my place of employment. My argument has been that LINQ is a consistent way of querying anything that supports IEnumerable (and others), not just databases. But, when using it to query databases, you get the added benefit of having all your queries strongly typed. You don't get this when doing inline SQL or calling stored procedures. This benefit is huge when entity definitions changes. The compiler will do all the work for you.

blocks|key|735939|text|我认为你也可以让他的项目和他的个人技能与最新的工具和开发保持同步。只是作为对上述所有内容的额外奖励。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|735940|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 think you could make also make the case that he'd be keeping both the project and his personal skill set in step with the latest tools and developments... just as a bonus to all of the above.

blocks|key|2347808|text|午餐时间。将你的代码投影到屏幕上，并展示如何在2到3行代码中重写他的20行代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2347809|几乎所有我看过的人都买下了。|2347810|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|$]]

Brown bag lunch session. Project your code on a screen and show how his 20 lines of code can be re-written in 2 or 3. 

That's pretty much sold everyone I've shown it to.

blocks|key|2036155|text|向他们展示my+projection+demo，并询问他们在ADO.NET中做同样的事情需要多少代码，然后指出，在现实世界中，可能会有存储库和服务，通过LINQ预测几乎是免费的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2036156|然后给他们看parallel+extensions+in+.NET+4。|2036157|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.teamb.com/craigstuntz/2009/12/31/38500/|1|http://channel9.msdn.com/posts/DanielMoth/VS2010-Parallel-Computing-Features-Tour/^0|5|I|0|0|6|T|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Show them <a href="http://blogs.teamb.com/craigstuntz/2009/12/31/38500/" rel="nofollow noreferrer" title="Projecting Onto a Presentation Model with the Entity Framework and ASP.NET MVC">my projection demo</a> and ask them how much code it would take to do the same thing in ADO.NET. Then point out that in the real world there would probably be repositories and services in between, which you get nearly free with LINQ projections.

Then show them the <a href="http://channel9.msdn.com/posts/DanielMoth/VS2010-Parallel-Computing-Features-Tour/" rel="nofollow noreferrer">parallel extensions in .NET 4</a>.

blocks|key|2347605|text|以下是一些好处：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2347606|2347607|您不仅可以查询数据库，还可以使用相同语法查询XML文件或任何对象集合-这在长期运行时很有用|unordered-list-item|offset|length|style|BOLD|2347608|Usign参数更简单，无需担心，例如SQL注入|2347609|<代码>H19您可以跨关系<代码>E110查询<代码>E211而无需显式联接、|2347610|2347611|2347612|我所说的最大的好处是第一点，相同和简单的语法。|2347613|但是，如果您的同事是数据库领域的专家，他可能不想立即转换。LINQ不会带来直接的好处，特别是在正在进行的项目上，但在我看来，它甚至在中期阶段也会让你更有效率。|2347614|entityMap^0|0|0|G|I|0|5|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|10|8|@$F|11|G|12|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|E|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|16|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|17|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|U|$]]

Some of the benefits:

<ul>
<li>You can query not just databases, but XML files or any object collection with the same syntax - this is useful on the long run</li>
<li>Usign parameters is easier, no need
to worry about e.g. SQL injections</li>
<li>You can query across relationships 
without having to explicitly join,
<a href="http://www.linqpad.net/WhyLINQBeatsSQL.aspx" rel="nofollow noreferrer">like this</a></li>
</ul>

The biggest benefit of all I would call is the first point, the same and simple syntax.

However if your colleague is an expert in the database field he might not want to switch immediately. LINQ does not bring immediate benefits, especially not on ongoing projects, but it makes you more efficient even on mid term in my opinion.

blocks|key|735402|text|告诉他们你已经重新考虑过了:你现在不喜欢LINQ，认为这是一种糟糕的方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|735403|这应该能起到作用。开个玩笑(主要是)。|735404|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|$]]

Tell them that you've reconsidered: you now dislike LINQ and think its an awful way to go.

That should do the trick. Just kidding (mostly).

How do you promote and/or sell LINQ syntax to colleague that doesn't see the benefit over the manual way of doing thing?

For an example using Linq to Entity/Sql instead of using plain ado.net without any LINQ.

How to promote and/or sell LINQ to colleague?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

你如何推广和/或推销LINQ语法给那些看不到手动方式的好处的同事？例如，使用LINQ to Entity/Sql而不是不带任何Linq的普通ado.net。

问如何向同事推广和/或销售LINQ？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何向同事推广和/或销售LINQ？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何向同事推广和/或销售LINQ？
EN