vb.net中Window.document的等效属性是什么?

本文介绍了vb中Window.document的等效属性是什么?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

大家好， vb中Window.document的等效属性是什么? Window.document是vb 6.0中的属性.vb中的等效属性是什么? vb中的Web浏览器.document属性可用，但我希望vb中的Window.document等效属性. 谢谢， Jayawant.

Hi All, What is equivalent property of Window.document in vb? Window.document it is the property in vb 6.0.What is equivalent property in vb? in vb Web browser.document property is available,but I want Window.document equivalent property in vb. Thanks, Jayawant.

推荐答案

首先，请参阅我对该问题的评论. 我认为您是从错误的角度来解决问题.您似乎认为那些不同的库是全息的(在这种意义上: en.wikipedia/wiki/Homology_%28biology%29 [ ^ ]).他们不是！ (哦，谢天谢地！) 首先，所采用的方法太不同了，因为系统和技术(如果VB6可以使用技术").简而言之，.NET库非常出色且与众不同. VB6在创建之初就完全是错误的，比许多旧的语言和库要差得多. 迁移是可能的，尤其是VB6遗留代码的编写非常准确，这种情况很少，几乎永远不会发生(体面的开发人员通常不同意处理VB6). 请参阅以下讨论: social.msdn.microsoft/Forums/zh/vbgeneral/thread/caea0ff1-7177-48bc-88cf-4db4f326a0ef [ ^ ]， msdn.microsoft/en-us/vstudio/ee373823 [ ^ ]. 如果您使用的是Google，则可以找到一些自动化迁移的解决方案. 我个人知道使用自动化进行大量迁移的尝试.我不知道一个成功的故事:-( 正确的方法是从零开始学习.NET方法，尝试使自己摆脱可能已经沉迷的想法.

—SA

First, please see my comment to the question. I think you are approaching the problem from the wrong side. It looks like you think that those different libraries are holological (in this sense: en.wikipedia/wiki/Homology_%28biology%29[^]). They are not! (Oh, thanks goodness!) The approached are too different, first of all, because the systems and technologies (if one can VB6 features a "technology"). In a nutshell, .NET libraries are pretty good and different; and VB6 is something which was completely wrong at the moment of its creations, much, much worse than many much older languages and libraries. The migration is possible, especially of VB6 legacy code is written very accurately, which is rarely, almost never a case (a decent developer usually would not agree to deal with VB6). Please see this discussion: social.msdn.microsoft/Forums/en/vbgeneral/thread/caea0ff1-7177-48bc-88cf-4db4f326a0ef[^], msdn.microsoft/en-us/vstudio/ee373823[^]. If you Google, you will be able to find some solutions for automation migration. I personally know some very intensive attempts to migrate using some automation. I don''t know a single success story :-( The right approach would be to learn .NET approaches from scratch, trying to free yourself from the ideas you might have been preoccupied with.

—SA