单声道和​​window.external [英] Mono and window.external

查看:215
本文介绍了单声道和​​window.external的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这将是一个Windows窗体应用程序通过的ClickOnce部署。 该计划是使用WebBrowser控件公开一个Web应用程序,它使用的Active-X控件。使用window.external和InvokeScript,对象将被替换为引用注册免费的COM对象(SXS)。我知道这听起​​来像一个烂摊子,但它是一个小恶,我在紧张的日程安排。最终,SXS部分可以更换,并希望在服务器端code能够更好的东西进行更新。 会不会有这个严重的性能问题?多少麻烦我会为问这个?

This will be a Windows Forms application deployed through ClickOnce. The plan is to use the WebBrowser control to expose a web application that makes use of Active-X controls. Using window.external and InvokeScript, the objects will be replaced with references to Reg-Free COM objects (SXS). I know this sounds like a mess, but it's a lesser evil, and I'm on a tight schedule. Eventually, the SXS part can be replaced, and hopefully the server-side code can be updated with something better. Will there be serious performance problems with this? How much trouble am I asking for with this?

将目标定位.NET 2.0使得它更容易有code,它是便携式的单声道和.NET之间? 是VB.NET code麻烦移植到单声道?我假设它不应该是什么? (我用VB6的程序员的工作)。

Will targetting .NET 2.0 make it easier to have code that is portable between Mono and .NET? Is VB.NET code troublesome to port to Mono? I'm assuming it shouldn't be? (I am working with VB6 programmers).

该文档说在Mono下window.external不可用。这听起来像有计划地实现这一点。它是安全的只使用window.external现在,等待单来实现它? 或者,有没有办法来模拟这一点?

The docs say that window.external is not available under Mono. It sounds like there are plans to implement this. Is it safe to just use window.external now and wait for Mono to implement it? Or, is there a way to emulate this?

我有其他的计划,慢慢地使code更便携,而且我希望我可以用这个作为一种方法(阅读:漏洞),使其能够

I have other plans to slowly make the code more portable, and I'm hoping I can use this as a sort of method (read: loophole) to make it possible.

如果您对心灵的态度和状态的建议,我会很高兴听到他们的声音了。但是请尽量先回答我的主要关注点。谢谢你。

If you have suggestions on attitudes and states of mind, I'd be happy to hear them too. But please try to answer my main concerns first. Thank you.

推荐答案

我不明白到底你正在尝试做的,但我看到具体的话我可以回答:

I don't understand exactly what you are trying to do, but I see specific words I can respond to:

  • 在单不支持的ClickOnce。
  • 在单不支持ActiveX。有一些COM的东西,但我不知道它是怎么完成。
  • 在Mono的WebBrowser控件支持基本的操作,但是window.external是非常先进的功能,这是非常具体的IE浏览器。目前还没有工作,被放进了WebBrowser控件,我看不出任何变化很快,除非有人有助于你所需要的。

将针对.NET 2.0使得它更容易有code,它是便携式的单声道和.NET之间?

Will targeting .NET 2.0 make it easier to have code that is portable between Mono and .NET?

我认为这是反对针对.NET 3.5,而不是NET 1.1。在.NET 2.0类库比.NET 3.0 / 3.5的人(不WPF,没有WF,有限的WCF)更加完整。但是,如果你只是想C#3的功能,如LINQ,所有的C#3应该很好地工作。

I assume this is opposed to targeting .NET 3.5, and not .NET 1.1. The .NET 2.0 class libraries are much more complete than the .NET 3.0/3.5 ones (no WPF, no WF, limited WCF). However, if you just want C# 3 features like LINQ, all of C# 3 should work fine.

时VB.NET code麻烦移植到单?

Is VB.NET code troublesome to port to Mono?

C#是肯定比VB.Net在Mono支持。该VB.Net编译器是当前版本8.0版(2005年)。在VB.Net运行时类库也是不完整的。 (虽然你可以完全避免这一点,仍然使用VB.Net。)

C# is definitely better supported than VB.Net on Mono. The VB.Net compiler is currently version version 8.0 (2005). The VB.Net runtime class library is also not complete. (Though you can completely avoid that and still use VB.Net.)

这篇关于单声道和​​window.external的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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