msscript.ocx 从哪里安装
我在我的应用程序中使用 msscript.ocx,它是 Windows 的 ActiveX 脚本主机。
尽管我希望能够对高度可定制的 XP 嵌入式(XPe)使用相同的功能。
1.我想知道在XPe上是否可以选择性安装msscript.ocx?
2.它从哪里安装,IE?
3.或者它是在XPe安装过程中安装的Windows核心组件吗?(我知道可以取消注册它,但它可以是可选安装)
回答任何或所有这些问题将对我有很大帮助。
提前致谢。
萨姆.
I'm using msscript.ocx in my application which is an activex scripting host for windows.
Although I want to be able to use the same for XP embedded(XPe) which's highly customizable.
1.I want to know whether on XPe, msscript.ocx can be optionally installed or not?
2.Where does it get installed from, IE?
3.Or is it a windows core component which gets installed during the XPe setup?(I know one can unregister it, but can it be an optional installation)
Answering any or all of these questions will be of great help to me.
Thanks in advance.
Sam.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
Microsoft 的 MSScript.ocx 库文档在这个问题上有些矛盾。简而言之,从 Windows 2000 开始,MSScript.ocx 库成为 Windows 操作系统的一部分。 Windows 2000、XP 和 2003 的后续 Service Pack 包含错误修复 (1、2,3) 对于这个库。从那时起,该库仍然是 Windows 32 位部分的一部分,并且仍然包含在 Windows 7/2008 R2 中。即使 64 位版本的 Windows 仍然包含 msscript.ocx 和 WOW64< /a> 在 C:\Windows\SysWOW64 中。
有关该库发行的一些历史,请继续阅读。
Msscript.ocx 最初作为“可选”库包含在 Visual Studio 6 CD 中 - 可选意味着它必须手动安装。虽然该库是 Visual Studio 的一部分,但从 Windows 2000 开始,它已迁移到 Windows 操作系统的一部分。
这就是混乱产生的地方。由于 msscript.ocx 被视为 VS6 和 Windows 2000 的组件,因此更新以服务包的形式分发给两者。即使在 VS6 的最后一个服务包发布后,还需要为旧操作系统分发其他错误修复程序,因此需要单独的 下载 是专门针对 Windows 95、98 和 NT4 创建的。
此下载针对较旧的操作系统,因为它已成为“现代”版本的 Windows 中操作系统的一部分。如果您使用的是 Windows 2000 或更高版本,则无需下载,并且根据我的经验,可能会导致兼容性问题。
Microsoft's documentation of the MSScript.ocx library is somewhat contradictory on this issue. The short answer is, starting with Windows 2000, the MSScript.ocx library became part of the Windows OS. Subsequent service packs for Windows 2000, XP, and 2003 included bug fixes (1,2,3) for this library. Since that time, the library has remained part of the 32bit portion of Windows and is still included with Windows 7/2008 R2. Even 64bit versions of Windows still include msscript.ocx with WOW64 in C:\Windows\SysWOW64.
For a little history of this library's distribution keep reading.
Msscript.ocx was originally included on the Visual Studio 6 CD as a "optional" library - optional meaning it had to be manually installed. While the library was part of Visual Studio, it was migrated to being part of the Windows OS starting with Windows 2000.
This is where the confusion comes into play. Since msscript.ocx is considered to be a component of both VS6 and Windows 2000, updates were distributed in service packs for both. Even after the last service pack for VS6 was released, additional bug fixes needed to be distributed for older OS's, so a separate download was created specifically targeting Windows 95, 98 and NT4.
This download is targeted for older OS's for the simple fact that it had become a part of the OS in "modern" versions of Windows. If you are using Windows 2000 or greater, the download is unnecessary and - in my experience - can cause compatibility problems.
我认为它没有随 Windows XP 一起提供(不是 100% 确定)...
但最好的选择是随安装程序一起提供(即使已提供,也可以将其删除)。关于安装-你可以把它放在你想要的地方(在Program Files的程序文件夹中就可以),重要的是注册它。
制作安装程序的最佳选择 - Wix
编辑: 参考
我想这回答了你的问题......
I think it is not shipped with Windows XP(not a 100% sure)...
But the best choice is to ship it with your installer(even if it was shipped, it can be removed). About the installing - you can put it where you want (in the program folder in Program Files is ok), the important thing is to register it.
The best choice for making installers - Wix
EDIT: reference
I think this answers your question....
对于那些在 MSSCRIPT.OCX 工作时遇到问题的用户,请执行以下操作:
转到项目设置中的引用:
微软脚本控制1.0
微软脚本运行时
Microsoft Scriptlet Library
检查所有这些。
您需要更改开发环境才能生成应用程序的 32 位版本,这对于大多数应用程序来说并不重要。
对于这个转到项目,
然后选择属性,
选择编译,
目标CPU:x86
在你的代码中,我使用的是Visual Studio 2019,
For those having issues getting MSSCRIPT.OCX to work do the following:
Go to References in Project settings:
Microsoft Script Control 1.0
Microsoft Scripting Runtime
Microsoft Scriptlet Library
Check all those on.
you'llneed to change your development environment to produce a 32 bit version of your appliation, which for most apps won't matter.
For this goto Project,
then select Properties,
select Compile,
Target CPU: x86
In your code, and i'm using visual studio 2019,