在一个应用程序中使用来自不同供应商的控件 [英] using controls from different vendors in one application

查看:68
本文介绍了在一个应用程序中使用来自不同供应商的控件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是Dev Express,Infragistics和其他一些控制人员的新手。我只想知道在应用程序中同时使用它们时可能遇到的问题。

I am new to Dev Express, Infragistics and some other control stuff. I Just want know what are the possible problems I might encounter when I use both of them in my application.

谢谢

推荐答案

这取决于您的应用程序,但是在非Web客户端中使用来自各种供应商的控件所带来的最大风险之一来自意外方向-您可能会发生冲突与您的appdomain中的其他内容。假设您要开发一个将您的应用程序公开给另一个应用程序的插件,反之亦然。如果使用了多个供应商的控件,则名称空间冲突的可能性会更高。

It depends on your application, but one of the biggest risks you run in using controls from a variety of vendors in a non-web client comes from an unexpected direction - you may conflict with other things in your appdomain. Let's say that you either want to develop a plugin that exposes your application to another application or vice versa. If you have used controls from several vendors, the likelihood of a namespace collision is much higher.

这很重要,因为例如,DevExpress随时间推移以重要方式改变了名称空间的组织,并且您很容易遇到插件拒绝加载的情况因为它需要加载冲突版本的控件框架。此时,您唯一的选择是使用单独的appdomain来保存您的插件。对于某些任务来说这很好,但是我可以从经验中告诉您,有一些主要的应用程序在公开其API时根本没有考虑到这一点。

This is important because, for example, DevExpress have changed the organization of their namespaces in important ways over time, and you could easily encounter a situation where your plugin refuses to load because it requires loading a conflicting version of a controls framework. Your only option at that point is to use a separate appdomain to hold your plugin. This is fine for some tasks, but I can tell you from experience that there are major applications out there that do not take this into account whatsoever when exposing their API.

给出.NET市场中主要控件供应商的数量有限,因此需要注意您的应用程序不会对此类冲突开放。

Given the limited number of major controls vendors in the .NET marketplace, you need to be careful that your application doesn't open itself up to these kinds of conflicts.

这篇关于在一个应用程序中使用来自不同供应商的控件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆