Management wants us to switch to Infragistics. But my boss says that any 3rd party is destined to fail, and at that point there won't be anything we can do about it.
管理层希望我们切换到Infragistics。但是我的老板说任何第三方都注定要失败,那时我们就无法做任何事情。
Is he right, is he wrong? I don't know.
他是对的,他错了吗?我不知道。
What are your opinions, is it better to use something developed inside the company, or do you prefer something like DevExpress, Infragistics, Krypton to name a few or is there something else even better that you would recommend instead?
您有什么看法,使用公司内部开发的东西更好,或者您更喜欢DevExpress,Infragistics,Krypton这样的东西,还是有其他更好的建议?
I'd very much appreciate your thoughts, and experience on the matter.
我非常感谢您对此事的想法和经验。
Thank you in advance.
先感谢您。
9 个解决方案
#1
4
When shopping for 3rd party controls, look for the option to purchase source code (for a reasonable price). With source code you should be able to make any necessary changes to the components to keep them running well in your environment.
购买第三方控件时,请查找购买源代码的选项(价格合理)。使用源代码,您应该能够对组件进行任何必要的更改,以使它们在您的环境中良好运行。
The Krypton Suite of controls from Component Factory does just this. Phil offers the source code for the entire suite for an amazing price (currently less than $400). I have used the Krypton Suite in my development for a year now and I have been extremely pleased with it. Krypton gives me the power to create shrink wrapped software with Office 2007 UI look and feel with consistency far beyond any other toolkit I tried. Phil is also very active in the support forums and provides you a direct link to the development path of the software.
Component Factory的Krypton控件套件就是这样做的。 Phil以惊人的价格(目前低于400美元)提供整个套件的源代码。我已经在我的开发中使用了Krypton Suite一年了,我对它非常满意。 Krypton让我有能力创建具有Office 2007 UI外观和感觉的收缩包装软件,其一致性远远超出我试过的任何其他工具包。 Phil在支持论坛中也非常活跃,并为您提供了与软件开发路径的直接链接。
#2
2
.NET3.5 SP1 is really matured to do ASP.NET and standalone UI development(WPF and Silverlight). What is your main criteria to go for third party components and frameworks. If you just need some charting or any other financial domain tools and control yeah you need to consider third party compoenents for a faster turnaround. Other than that I would see the .NET framework itself has rich libraries to do most of the things.
.NET3.5 SP1非常成熟,可用于ASP.NET和独立UI开发(WPF和Silverlight)。第三方组件和框架的主要标准是什么?如果您只需要一些图表或任何其他金融领域工具并控制是的,您需要考虑第三方组件以获得更快的周转时间。除此之外,我会看到.NET框架本身有丰富的库来完成大部分工作。
#3
1
I don't think it's entirely bad to rely on third parties. Some are very reputable and will do a great job of supporting you. But on the other hand, some are terrible to work with even if they stay in business. I don't know anything about the frameworks you've mentioned, though.
我不认为依赖第三方是完全不好的。有些是非常有信誉的,并且会很好地支持你。但另一方面,即使他们继续经营,有些人也很难与他们合作。但是,我对你提到的框架一无所知。
Have you considered an open source framework? That way you can still work on it yourself if all else fails. Of course, you have to take into account licensing requirements when doing this, but I think it's definitely something you should look into if it's appropriate for the project.
您是否考虑过开源框架?这样,如果其他所有方法都失败,您仍然可以自己处理它。当然,在执行此操作时,您必须考虑许可要求,但我认为如果它适合项目,您肯定应该考虑这些要求。
#4
0
As long as you have access to the source code of the library and are able to modify it and distribute the modified library without paying any royalties, your boss's fears are unfounded.
只要您可以访问库的源代码并且能够修改它并分发修改后的库而无需支付任何版税,那么老板的担心是没有根据的。
I'd go for DevExpress myself, but they are quite pricey when compared to the other frameworks.
我自己会去DevExpress,但与其他框架相比,它们相当昂贵。
#5
0
I think that your boss's concern could be better phrased as "One of these days we're gonna need to change the 3rd party control in a way that requires modifying it's source." Depending on the license that comes with the third party control, this might get sticky. For something like a UI control, in my experience .NET makes it pretty easy to make whatever it is you need anyway.
我认为你老板的关注可以更好地表达为“有一天我们需要以某种方式改变第三方控制,这需要修改它的来源。”根据第三方控件附带的许可证,这可能会变得棘手。对于类似UI控件的东西,根据我的经验,.NET可以很容易地制作出你需要的任何东西。
Maybe as a way to resolve the debate you could propose to knock out a quick prototype of whatever control(s) you'd otherwise need to borrow. That will give you insight as to (a) whether the third party library is needed and (b) what requirements you have of a third party library should you choose to go in that direction.
也许作为一种解决争论的方法,你可以建议删除你需要借用的任何控制的快速原型。这将使您了解(a)是否需要第三方库以及(b)如果您选择朝这个方向前进,您对第三方库有何要求。
#6
0
The important thing to plan for when using 3rd party controls is continuity. If they do go under, what does that mean to you? How much are you relying on their framework, and how much work would it be to switch to something else? IS there something else that does what you need?
使用第三方控件时计划的重要事项是连续性。如果他们确实失败了,这对你意味着什么?您依赖他们的框架多少,以及切换到其他东西需要做多少工作?还有其他什么可以满足您的需求吗?
If you have source code for the component in question, it puts you in a much better position - you can at least fix bugs and possibly even maintain/extend it yourself. On the other end of the spectrum is tightly controlled software, where you have to renew every year and it expires if you don't. If you're using something like this, if they go under, it forces your hand, and you'll have to do something.
如果您有相关组件的源代码,它会让您处于更好的位置 - 您至少可以修复错误,甚至可能自己维护/扩展错误。在频谱的另一端是严格控制的软件,你必须每年更新,如果你不这样做,它就会过期。如果你正在使用这样的东西,如果它们被摧毁,它会强迫你的手,你将不得不做一些事情。
It's really a balancing act. Saving you work/money vs Probability of them disappearing vs Relying on a 3rd party.
这真的是一种平衡行为。拯救你的工作/金钱与他们的概率消失与依赖第三方。
I once had a boss that was like yours. The thing they miss is that you're entirely relying on 3rd party. If you're using .NET, you're trusting that Microsoft is not going to go under (probably not..), discontinue it (maybe), or radically change it (quite possible). Of course he's gone now, and we've since started using a handful of 3rd party controls (some open source) that have saved us hundreds of hours of dev time, or just let us do features we never would have done otherwise (because it would take too long).
我曾经有一个和你一样的老板。他们想念的是你完全依赖第三方。如果您正在使用.NET,那么您就相信微软不会陷入困境(可能不会......),停止它(可能),或者彻底改变它(很可能)。当然他现在已经走了,我们已经开始使用一些第三方控件(一些开源),这些控件为我们节省了数百小时的开发时间,或者只是让我们做一些我们从未做过的功能(因为它需要太长时间)。
#7
0
If your company makes U.I. then by all means develop and maintain your controls in house. If that is not your main business objective you should find a code vendor that offers source code for the control ( devexpress, telerik...) And when you implement these controls give your self a layer of abstraction so that it is simpler to switch vendors in the future.
如果贵公司生产U.I.然后通过各种方式在内部开发和维护您的控件。如果这不是您的主要业务目标,您应该找到一个代码供应商,为控件提供源代码(devexpress,telerik ...)。当您实现这些控件时,为您自己提供一个抽象层,以便更换供应商更简单在将来。
#8
0
Thank you very much for your insights. I've used Krypton myself but only the part that is free. I think it's more of a "We want it to look slick". I share my boss's concern with using 3rd party controls, but I also agree with you guys in that it's far better to concentrate on the task than on providing controls that look good.
非常感谢您的见解。我自己使用过Krypton,但只使用了免费的部分。我认为这更像是“我们希望它看起来光滑”。我与老板分享使用第三方控件的担忧,但我同意你们的意见,因为专注于任务而不是提供看起来不错的控件要好得多。
The question the manager faced my boss with when he said that it's a bad idea to use Infragistics was "But can you do something similar in a reasonable amount of time ?". The answer was obviously "No".
当经理面对我的老板时,他说使用Infragistics是一个坏主意的问题是“但你能在合理的时间内做类似的事吗?”。答案显然是“不”。
I'll try suggesting Krypton Toolkit, I've used it a bit in the past as I've said before, I did have some trouble with it. I think the datagrid is the main focus of the problem, since most of the toolkits have options for customizing the appearence.
我会尝试建议使用Krypton Toolkit,我之前已经使用过它,因为我之前说过,我确实遇到了一些问题。我认为数据网格是问题的主要焦点,因为大多数工具包都有自定义外观的选项。
Again, thanks so much for your answers.
再次,非常感谢您的回答。
#9
0
I think when you buy third party controls you should think about the value you receive for the money you pay. There are dinosaur vendors like Telerik, Syncfusion, DevExpress, Infragistics which offer GUI with good quality and support, but they are not very cheap, because the brand costs money. There are other great WinForms suites coming from a small vendors such as ComponentFactory, DevComponents, VIBlend, Nevron which offer a good looking controls for WinForms in Office2007 style but much cheaper.
我认为,当您购买第三方控件时,您应该考虑您所支付的款项所获得的价值。有像Telerik,Syncfusion,DevExpress,Infragistics这样的恐龙供应商提供优质和支持的GUI,但它们并不便宜,因为这个品牌需要花钱。还有来自小型供应商的其他优秀WinForms套件,如ComponentFactory,DevComponents,VIBlend,Nevron,它们为Office2007风格的WinForms提供了良好的控制,但便宜得多。
#1
4
When shopping for 3rd party controls, look for the option to purchase source code (for a reasonable price). With source code you should be able to make any necessary changes to the components to keep them running well in your environment.
购买第三方控件时,请查找购买源代码的选项(价格合理)。使用源代码,您应该能够对组件进行任何必要的更改,以使它们在您的环境中良好运行。
The Krypton Suite of controls from Component Factory does just this. Phil offers the source code for the entire suite for an amazing price (currently less than $400). I have used the Krypton Suite in my development for a year now and I have been extremely pleased with it. Krypton gives me the power to create shrink wrapped software with Office 2007 UI look and feel with consistency far beyond any other toolkit I tried. Phil is also very active in the support forums and provides you a direct link to the development path of the software.
Component Factory的Krypton控件套件就是这样做的。 Phil以惊人的价格(目前低于400美元)提供整个套件的源代码。我已经在我的开发中使用了Krypton Suite一年了,我对它非常满意。 Krypton让我有能力创建具有Office 2007 UI外观和感觉的收缩包装软件,其一致性远远超出我试过的任何其他工具包。 Phil在支持论坛中也非常活跃,并为您提供了与软件开发路径的直接链接。
#2
2
.NET3.5 SP1 is really matured to do ASP.NET and standalone UI development(WPF and Silverlight). What is your main criteria to go for third party components and frameworks. If you just need some charting or any other financial domain tools and control yeah you need to consider third party compoenents for a faster turnaround. Other than that I would see the .NET framework itself has rich libraries to do most of the things.
.NET3.5 SP1非常成熟,可用于ASP.NET和独立UI开发(WPF和Silverlight)。第三方组件和框架的主要标准是什么?如果您只需要一些图表或任何其他金融领域工具并控制是的,您需要考虑第三方组件以获得更快的周转时间。除此之外,我会看到.NET框架本身有丰富的库来完成大部分工作。
#3
1
I don't think it's entirely bad to rely on third parties. Some are very reputable and will do a great job of supporting you. But on the other hand, some are terrible to work with even if they stay in business. I don't know anything about the frameworks you've mentioned, though.
我不认为依赖第三方是完全不好的。有些是非常有信誉的,并且会很好地支持你。但另一方面,即使他们继续经营,有些人也很难与他们合作。但是,我对你提到的框架一无所知。
Have you considered an open source framework? That way you can still work on it yourself if all else fails. Of course, you have to take into account licensing requirements when doing this, but I think it's definitely something you should look into if it's appropriate for the project.
您是否考虑过开源框架?这样,如果其他所有方法都失败,您仍然可以自己处理它。当然,在执行此操作时,您必须考虑许可要求,但我认为如果它适合项目,您肯定应该考虑这些要求。
#4
0
As long as you have access to the source code of the library and are able to modify it and distribute the modified library without paying any royalties, your boss's fears are unfounded.
只要您可以访问库的源代码并且能够修改它并分发修改后的库而无需支付任何版税,那么老板的担心是没有根据的。
I'd go for DevExpress myself, but they are quite pricey when compared to the other frameworks.
我自己会去DevExpress,但与其他框架相比,它们相当昂贵。
#5
0
I think that your boss's concern could be better phrased as "One of these days we're gonna need to change the 3rd party control in a way that requires modifying it's source." Depending on the license that comes with the third party control, this might get sticky. For something like a UI control, in my experience .NET makes it pretty easy to make whatever it is you need anyway.
我认为你老板的关注可以更好地表达为“有一天我们需要以某种方式改变第三方控制,这需要修改它的来源。”根据第三方控件附带的许可证,这可能会变得棘手。对于类似UI控件的东西,根据我的经验,.NET可以很容易地制作出你需要的任何东西。
Maybe as a way to resolve the debate you could propose to knock out a quick prototype of whatever control(s) you'd otherwise need to borrow. That will give you insight as to (a) whether the third party library is needed and (b) what requirements you have of a third party library should you choose to go in that direction.
也许作为一种解决争论的方法,你可以建议删除你需要借用的任何控制的快速原型。这将使您了解(a)是否需要第三方库以及(b)如果您选择朝这个方向前进,您对第三方库有何要求。
#6
0
The important thing to plan for when using 3rd party controls is continuity. If they do go under, what does that mean to you? How much are you relying on their framework, and how much work would it be to switch to something else? IS there something else that does what you need?
使用第三方控件时计划的重要事项是连续性。如果他们确实失败了,这对你意味着什么?您依赖他们的框架多少,以及切换到其他东西需要做多少工作?还有其他什么可以满足您的需求吗?
If you have source code for the component in question, it puts you in a much better position - you can at least fix bugs and possibly even maintain/extend it yourself. On the other end of the spectrum is tightly controlled software, where you have to renew every year and it expires if you don't. If you're using something like this, if they go under, it forces your hand, and you'll have to do something.
如果您有相关组件的源代码,它会让您处于更好的位置 - 您至少可以修复错误,甚至可能自己维护/扩展错误。在频谱的另一端是严格控制的软件,你必须每年更新,如果你不这样做,它就会过期。如果你正在使用这样的东西,如果它们被摧毁,它会强迫你的手,你将不得不做一些事情。
It's really a balancing act. Saving you work/money vs Probability of them disappearing vs Relying on a 3rd party.
这真的是一种平衡行为。拯救你的工作/金钱与他们的概率消失与依赖第三方。
I once had a boss that was like yours. The thing they miss is that you're entirely relying on 3rd party. If you're using .NET, you're trusting that Microsoft is not going to go under (probably not..), discontinue it (maybe), or radically change it (quite possible). Of course he's gone now, and we've since started using a handful of 3rd party controls (some open source) that have saved us hundreds of hours of dev time, or just let us do features we never would have done otherwise (because it would take too long).
我曾经有一个和你一样的老板。他们想念的是你完全依赖第三方。如果您正在使用.NET,那么您就相信微软不会陷入困境(可能不会......),停止它(可能),或者彻底改变它(很可能)。当然他现在已经走了,我们已经开始使用一些第三方控件(一些开源),这些控件为我们节省了数百小时的开发时间,或者只是让我们做一些我们从未做过的功能(因为它需要太长时间)。
#7
0
If your company makes U.I. then by all means develop and maintain your controls in house. If that is not your main business objective you should find a code vendor that offers source code for the control ( devexpress, telerik...) And when you implement these controls give your self a layer of abstraction so that it is simpler to switch vendors in the future.
如果贵公司生产U.I.然后通过各种方式在内部开发和维护您的控件。如果这不是您的主要业务目标,您应该找到一个代码供应商,为控件提供源代码(devexpress,telerik ...)。当您实现这些控件时,为您自己提供一个抽象层,以便更换供应商更简单在将来。
#8
0
Thank you very much for your insights. I've used Krypton myself but only the part that is free. I think it's more of a "We want it to look slick". I share my boss's concern with using 3rd party controls, but I also agree with you guys in that it's far better to concentrate on the task than on providing controls that look good.
非常感谢您的见解。我自己使用过Krypton,但只使用了免费的部分。我认为这更像是“我们希望它看起来光滑”。我与老板分享使用第三方控件的担忧,但我同意你们的意见,因为专注于任务而不是提供看起来不错的控件要好得多。
The question the manager faced my boss with when he said that it's a bad idea to use Infragistics was "But can you do something similar in a reasonable amount of time ?". The answer was obviously "No".
当经理面对我的老板时,他说使用Infragistics是一个坏主意的问题是“但你能在合理的时间内做类似的事吗?”。答案显然是“不”。
I'll try suggesting Krypton Toolkit, I've used it a bit in the past as I've said before, I did have some trouble with it. I think the datagrid is the main focus of the problem, since most of the toolkits have options for customizing the appearence.
我会尝试建议使用Krypton Toolkit,我之前已经使用过它,因为我之前说过,我确实遇到了一些问题。我认为数据网格是问题的主要焦点,因为大多数工具包都有自定义外观的选项。
Again, thanks so much for your answers.
再次,非常感谢您的回答。
#9
0
I think when you buy third party controls you should think about the value you receive for the money you pay. There are dinosaur vendors like Telerik, Syncfusion, DevExpress, Infragistics which offer GUI with good quality and support, but they are not very cheap, because the brand costs money. There are other great WinForms suites coming from a small vendors such as ComponentFactory, DevComponents, VIBlend, Nevron which offer a good looking controls for WinForms in Office2007 style but much cheaper.
我认为,当您购买第三方控件时,您应该考虑您所支付的款项所获得的价值。有像Telerik,Syncfusion,DevExpress,Infragistics这样的恐龙供应商提供优质和支持的GUI,但它们并不便宜,因为这个品牌需要花钱。还有来自小型供应商的其他优秀WinForms套件,如ComponentFactory,DevComponents,VIBlend,Nevron,它们为Office2007风格的WinForms提供了良好的控制,但便宜得多。