不同的API版本 [英] Different API versions

查看:161
本文介绍了不同的API版本的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

让我们说我有插件API。许多程序集实现了

插件API版本1.随着时间的推移插件接口更改为版本

2.您将如何处理实现旧API的程序集? />

Let''s say I have plug-in API. A number of assemblies implement
plug-in API version 1. Over time plug-in interface changes to version
2. How would you handle assemblies implementing old API?

推荐答案

在GAC中安装插件。然后版本可以共存,

是你想保留传统支持的。


" bazad" <无**** @ noreply.not>在消息中写道

news:sl ******************* @ STA01052.itron.com ...
Have the plug-in installed in the GAC. Then the version can coexist, that
is if you want to maintain legacy support.

"bazad" <no****@noreply.not> wrote in message
news:sl*******************@STA01052.itron.com...
假设我有插件API。许多程序集都实现了插件API版本1.随着时间的推移插件接口更改为版本
2.您将如何处理实现旧API的程序集?
Let''s say I have plug-in API. A number of assemblies implement
plug-in API version 1. Over time plug-in interface changes to version
2. How would you handle assemblies implementing old API?



在GAC中安装插件。然后版本可以共存,

是你想保留传统支持的。


" bazad" <无**** @ noreply.not>在消息中写道

news:sl ******************* @ STA01052.itron.com ...
Have the plug-in installed in the GAC. Then the version can coexist, that
is if you want to maintain legacy support.

"bazad" <no****@noreply.not> wrote in message
news:sl*******************@STA01052.itron.com...
假设我有插件API。许多程序集都实现了插件API版本1.随着时间的推移插件接口更改为版本
2.您将如何处理实现旧API的程序集?
Let''s say I have plug-in API. A number of assemblies implement
plug-in API version 1. Over time plug-in interface changes to version
2. How would you handle assemblies implementing old API?



在文章< OP ************* @ TK2MSFTNGP10.phx.gbl>中,Peter Rilling写道:
In article <OP*************@TK2MSFTNGP10.phx.gbl>, Peter Rilling wrote:
有插头-in安装在GAC中。然后版本可以共存,
如果你想保持传统支持。


将插件用于GAC是没有意义的。根据定义,插件只有一个版本



真正的问题是与更新版本的
$ b相同的过程$ b框架需要能够加载程序集。其中一些

程序集实现了当前的IPlugIn接口版本,而部分程序集未升级并实现了旧版本的

接口。你是如何处理的?

" bazad" <无**** @ noreply.not>在消息中写道
新闻:sl ******************* @ STA01052.itron.com ...
Have the plug-in installed in the GAC. Then the version can coexist, that
is if you want to maintain legacy support.
There is no point to use GAC for a plug-in. Plug-in by definition has
only one version.

The real problem is that the same process with a newer version of the
framework will need to be able to load assemblies. Some of these
assemblies implement the current IPlugIn interface version and some of
the assemblies were not upgraded and implement older version of the
interface. How do you handle that?
"bazad" <no****@noreply.not> wrote in message
news:sl*******************@STA01052.itron.com...
让's'说我有插件API。许多程序集都实现了插件API版本1.随着时间的推移插件接口更改为版本
2.您将如何处理实现旧API的程序集?
Let''s say I have plug-in API. A number of assemblies implement
plug-in API version 1. Over time plug-in interface changes to version
2. How would you handle assemblies implementing old API?




这篇关于不同的API版本的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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