Microsoft CCR 是否获得了关注？
微软的并发和协调运行时确实拯救了一个遇到重大死锁问题的项目。 从那时起，我发现我越来越频繁地使用它来处理几乎所有需要异步编码的事情，从而产生比以前运行更轻、更快的结果。 我可以诚实地说，它改变了我对多线程/多核开发的看法。 尽管我个人很喜欢 CCR，但网络上似乎很少有关于它的讨论，我想知道是否有人可以为此提供任何理由。 是否有更好的替代方案，或者缺乏微软的推广，或者人们只是对现有工具感到满意？
Microsoft's Concurrency and Coordination Runtime quite literally saved a project that was running into major issues with deadlocking. Since then I find that I use it more and more frequently for almost anything that requires asynchronous coding producing results that run lighter and faster than before. I can honestly state that it has transformed the way I think about multithread/multicore dev. Despite my personal love for CCR, there appears to be very little buzz surrounding it on the web and was wondering if anyone can offer any reason for this. Are there better alternatives, or is it a lack of promotion from MS, or are people simply happy with the existing tools?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我建议 TPL Dataflow 发布为.Net 4.5 的一部分，最终将取代 CCR。 CCR 中的大多数概念在 Dataflow 中都有类似物，尽管它不一定是直接的移植练习。
也就是说，Robotics Studio Developer 4 Beta 2，2011 年 11 月发布，包含 Silverlight 4 的 CCR 版本。
I would suggest that TPL Dataflow, to be released as part of .Net 4.5, will eventually supersede the CCR. Most concepts in the CCR have an analogue in Dataflow although it isn't necessarily a straightforward porting exercise.
That said, the Robotics Studio Developer 4 Beta 2, released November 2011, does include a version of the CCR for Silverlight 4.
据我所知，围绕它的许可有点痛苦。
我认为大多数人都在等待 .NET 4.0 中的并行扩展。 我知道这不完全是同一件事，但它仍然比目前框架中的内容要好得多 - 尽管延续的工作方式不同，但至少它们在那里:)
我怀疑并行扩展有比 CCR 做了更多的工作 - 尽管我确信 CCR 的工作也启发了 PFX 的一些设计。
The licensing around it is a bit of a pain, from what I remember.
I think most people are waiting for Parallel Extensions in .NET 4.0. I know it's not quite the same thing, but it's still a lot better than what's in the framework at the moment - and although the continuations don't work the same way, at least they're there :)
I suspect that Parallel Extensions has had rather more work on it than CCR - although I'm sure the CCR work inspired some of the design of PFX as well.
我个人也很喜欢 CCR...我当然没有在 .NET 或其他地方看到任何与它相当的东西。 我认为 Jon 是对的，这太糟糕了，它可能会被归为像我们这样的狂热粉丝的小众群体，而大多数主流 .NET 多线程可能会通过并行扩展来完成。
我对这种预测特别失望，因为我认为可以采取更多措施来推广它 - 比如说，也许可以将其放入企业可靠的异步消息总线类型框架中，我认为该框架在 .NET 中缺乏连贯的故事。 另外，通过查看 Microsoft CCR/DSS 站点，我可能永远不会想到尝试它。 .. 我不明白为什么它是以这种方式打包的 - 除了几家公司将其从机器人工具包中剥离出来并在 MS 认为它具有超越机器人技术的用途之前就使用它这一事实。
不管怎样，你并不孤单......而且还有很多其他 CCR“爱好者”。 这是一个简洁的基于“流”的 CodePlex 项目，它将 CCR 包装在一个有趣的流范例中。
I, too, have a personal love for the CCR... I certainly have not seen anything quite the equivalent of it in .NET or elsewhere. I think it's too bad that I think Jon's right and it will likely be relegated to a niche of enthusiastic fans like us, while most mainstream .NET multithreading will probably be done with the Parallel Extensions.
I'm particularly disappointed in this prognosis because I think more could be done to promote it - say maybe fit it into an enterprise reliable async message bus-type framework, which I think is lacking a coherent story in .NET. Also, from looking at the Microsoft CCR/DSS Site I would probably never have thought to try it... I don't understand why it was packaged up this way - other than the fact that several companies ripped it out of the Robotics toolkit and just ran with it before MS thought it had a purpose beyond robotics.
Anyway, you're not alone... and there are lots of other CCR 'enthusiasts' as well. Here's a neat 'flow' based CodePlex project that wraps the CCR in an interesting flow paradigm.
到目前为止，我一直很喜欢在两个主要项目中使用 CCR。 第一个很糟糕（没有真正理解因果关系模式的想法），第二个则进展顺利（网络爬虫）这
两个项目都利用基于消息的范例来避免等待缓慢运行的 IO 操作。 一旦解决了缺乏兼容的 ORM 映射器的问题，CCR 就非常适合使用。 （我正在考虑发布一些我编写的管道代码，以减轻其他人的心痛）
话虽如此，RX 看起来相当有趣。 我很好奇它在错误处理、速度和可靠性方面的比较如何。
I have been enjoying using the CCR in two major projects so far. The first one is terrible (didn't really get the Causality pattern idea) And the second one is coming along brilliantly (Web crawler)
Both projects are utilize the message based paradigm to avoid waiting for slow running IO operations. The CCR is quite good to work with once you solve the lack of a compatable ORM mapper. (I'm considering releasing some of the plumbing code that i've written to save other people the heart ache)
Having said that, RX looks quite interesting. I'm curious how it compares in terms of Error handling, speed and reliability.
Microsoft Robotics Studio 2008 R3 现已推出，并且免费供所有人使用。
Microsoft Robotics Studio 2008 R3 is now available and now free for everyone to use.