我在评估使用CAB的一个新的.NET 3.5的WinForm项目

过程

我计划使用Infragistics的工具，这是众所周知是CAB标准

虽然驾驶室让我专注于我的事业，而不是编码基本对接/登录/等code的直接上攻，我觉得我能由我自己来实现functionnality同级别相当radpidly（带增加了灵活性/反应的奖金你，当你拥有的code）。

我用它寻求人们对微软的CAB一些反馈：

你有没有遇到的问题/错误？ 请你觉得CAB节省你的时间？ 是否有额外的功能，我不知道（对接/登录/ WorkerThreads最佳做法？旁） 解决方案

我不得不使用CAB几年前的一些经验，我的结论是，它太复杂了，有一个陡峭的学习曲线。这样的好处是提供的只是不值得去加快速度与它的价格。但是不要把我的话，请尝试以下一些他们的实验室，看看你的想法。

杰里米米勒写了一个极好的一系列博客文章如何构建自己的CAB

http://$c$cbetter.com/blogs/jeremy.miller/archive/2007/07/25/the-build-your-own-cab-series-table-of-contents.aspx

这些都是值得一试，你可以只从那里你所需要的花费。

我的建议是，以获得与您的项目，而不是建立一个框架前面。随着项目的发展，你应该发现机会来重构code到基类和有效地从应用程序中收获了一个框架。

这样，你就结束了一个框架，以满足您的需求，大家对开发团队就明白了。不管你做什么不建立一个框架，前面 - 其实存在着路径毁： - ）

I'm in the process of evaluating the use of CAB for a new .net 3.5 winform project

I plan to use the Infragistics toolset, which is known to be 'CAB compliant'

While CAB has the immediate upside of letting me focus on my business instead of coding basic docking/login/etc code, I feel like I would be able to achieve the same level of functionnality quite radpidly by myself (with the added flexibility/reactivity bonus you have when you 'own' the code).

I'm seeking some feedback on Microsoft's CAB from people using it :

Have you experienced problems/bugs ? Do you feel like CAB saved your time ? Are there extra functionalities I don't know about (beside Docking/Login/WorkerThreads best practices?)

解决方案

I had some experience using CAB a couple of years ago and my conclusion was that it too complex and had a steep learning curve. As such the benefits it offered just weren't worth the price of getting up to speed with it. However don't take my word for it, try following some of their labs and see what you think.

Jeremy Miller wrote an excellent series of blog posts about building your own CAB

http://codebetter.com/blogs/jeremy.miller/archive/2007/07/25/the-build-your-own-cab-series-table-of-contents.aspx

these are worth a look as you could just take from there what you need.

My advice would be to get on with your project rather than build a framework up front. As the project develops you should spot opportunities to refactor code into base classes and effectively harvest a framework from your application.

That way you will end up with a framework that meets your needs, and that everyone on the development team will understand. Whatever you do don't build a framework up front - there lies the path to ruin :-)