COM->.NET - 无法访问重载方法
我正在尝试从 COM (jscript) 访问 .Net 库 (The Image Resizer)。
我已经尝试过 IDispatch 和类接口生成,以及相关类上的 [ClassInterface( ClassInterfaceType.AutoDual)] 。
有一个具有 3 个重载的方法:
Bitmap Build(object, ResizeSettings settings)
void Build(object source, object dest, string settings)
void Build(object source, object dest, ResizeSettings settings)
调用
Build("file",s); //works
以下两者都会生成“参数数量错误或属性分配无效”(JScript 运行时错误)
Build("file","file", s)
Build("file","file","settings
我找不到任何重载不能通过互操作工作的原因,特别是当参数计数不同时。 我错过了什么吗?
更新:这是方法定义的完整代码。第二个过载是无法访问的。不仅仅是这些方法 - 在每个重载方法中,我似乎只能访问第一个重载。这是一个未记录的 COM 错误/设计缺陷吗?
/// <summary>
/// Provides methods for generating resized images, and for reading and writing them to disk.
/// Use ImageBuilder.Current to get the current instance (as configured in the application configuration), or use ImageBuilder.Current.Create() to control which extensions are used.
/// </summary>
public class ImageBuilder : AbstractImageProcessor, IQuerystringPlugin
{
/// <summary>
/// Resizes and processes the specified source image and returns a bitmap of the result.
/// This method assumes that transparency will be supported in the final output format, and therefore does not apply a matte color. Use &bgcolor to specify a background color
/// if you use this method with a non-transparent format such as Jpeg.
/// </summary>
/// <param name="source">May be an instance of string (a physical path), VirtualFile, IVirtualBitmapFile, HttpPostedFile, Bitmap, Image, or Stream.</param>
/// <param name="settings">Resizing and processing command to apply to the.</param>
public virtual Bitmap Build(object source, ResizeSettings settings) {
BitmapHolder bh = new BitmapHolder();
Build(source, bh, settings);
return bh.bitmap;
}
/// <summary>
/// Resizes and processes the specified source image and stores the encoded result in the specified destination.
/// </summary>
/// <param name="source">May be an instance of string (a physical path or app-relative virtual path), VirtualFile, IVirtualBitmapFile, HttpPostedFile, Bitmap, Image, or Stream. app-relative virtual paths will use the VirtualPathProvider system</param>
/// <param name="dest">May be a physical path (string), or a Stream instance. Does not have to be seekable.</param>
/// <param name="settings">Resizing and processing command to apply to the.</param>
public virtual void Build(object source, object dest, ResizeSettings settings) {
ResizeSettings s = new ResizeSettings(settings);
I'm trying to access a .Net library (The Image Resizer) from COM (jscript).
I've tried both IDispatch and class interface generation, as well as [ClassInterface( ClassInterfaceType.AutoDual)] on the class in question.
There is a method with 3 overloads:
Bitmap Build(object, ResizeSettings settings)
void Build(object source, object dest, string settings)
void Build(object source, object dest, ResizeSettings settings)
Calling
Build("file",s); //works
The following both generate "Wrong number of arguments or invalid property assignment" (JScript runtime error)
Build("file","file", s)
Build("file","file","settings
I can't find any reason that overloads shouldn't work through interop, especially when the arg count differs.
Am I missing something?
Update: Here is the full code of the method definitions. The second overload is inacccessible. It's not just these methods - in every overloaded method, I only seem to be able to access the first overload. Is this a undocumented COM bug/design flaw?
/// <summary>
/// Provides methods for generating resized images, and for reading and writing them to disk.
/// Use ImageBuilder.Current to get the current instance (as configured in the application configuration), or use ImageBuilder.Current.Create() to control which extensions are used.
/// </summary>
public class ImageBuilder : AbstractImageProcessor, IQuerystringPlugin
{
/// <summary>
/// Resizes and processes the specified source image and returns a bitmap of the result.
/// This method assumes that transparency will be supported in the final output format, and therefore does not apply a matte color. Use &bgcolor to specify a background color
/// if you use this method with a non-transparent format such as Jpeg.
/// </summary>
/// <param name="source">May be an instance of string (a physical path), VirtualFile, IVirtualBitmapFile, HttpPostedFile, Bitmap, Image, or Stream.</param>
/// <param name="settings">Resizing and processing command to apply to the.</param>
public virtual Bitmap Build(object source, ResizeSettings settings) {
BitmapHolder bh = new BitmapHolder();
Build(source, bh, settings);
return bh.bitmap;
}
/// <summary>
/// Resizes and processes the specified source image and stores the encoded result in the specified destination.
/// </summary>
/// <param name="source">May be an instance of string (a physical path or app-relative virtual path), VirtualFile, IVirtualBitmapFile, HttpPostedFile, Bitmap, Image, or Stream. app-relative virtual paths will use the VirtualPathProvider system</param>
/// <param name="dest">May be a physical path (string), or a Stream instance. Does not have to be seekable.</param>
/// <param name="settings">Resizing and processing command to apply to the.</param>
public virtual void Build(object source, object dest, ResizeSettings settings) {
ResizeSettings s = new ResizeSettings(settings);
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
确实,COM 不“执行”方法重载。
但。请参阅 http://msdn.microsoft.com/ en-us/library/ms182197(v=vs.80).aspx 。
这是静态分析工具 FxCop 的文档页面。但其中有一些信息对 COM 开发人员很有用:
另请参阅
COM 互操作 (CCW) 中的重载 - IDispatch 名称包含后缀(_2、_3 等)
因此,通过 COM 层,您可以使用以下命令调用原始方法
True that COM doesn't "do" method overloading.
BUT. see http://msdn.microsoft.com/en-us/library/ms182197(v=vs.80).aspx .
This is a doc page on FxCop, a static analysis tool. But there's a tidbit of information there, which is useful for COM developers:
and also see
Overloads in COM interop (CCW) - IDispatch names include suffix (_2, _3, etc)
So, through the COM layer, you could call your original methods with
重载对于 COM 的互操作层不起作用。但是,您可以使用可选参数并隐藏 COM 层中的所有其他方法:
Overloading does not work for the interop layer to COM. You could however use optional parameters and hide all other methods from the COM layer: