用VC++ 6.0, VC++.NET 2003编译的程序能在XP下运行成功,在Vista下面不能运行.因为不会打安装包,所以不知道是不是打了安装包就可以在Vista下面运行了.但是很确定的一点是,Vista不像XP一样,复制可执行文件及相关动态链接库到system32文件夹就可以运行.
于是开始上网寻找解决办法.搜到很多网页,都在说Vista的兼容性不良,说有很多程序在Vista下面运行都不理想,甚至有很大问题.但我的程序比较小,并没有涉及到网络或数据库这些应用,所以我想应该问题不会很大.况且机子上有一些不知道哪里来的规模相当,功能相似的程序都运行正常.所以我在想也许问题应该没那么严重.(后来找到了那个程序的源码,是DELPHI做的,看到人家DELPHI的程序运行得那么好,我做VC的心里很不是滋味.)
继而转向微软新一代开发环境寻找解决方案.立即寻找VS2005.将GOOGLE所有的网页翻了一遍,无果.绝望中发现有微软官网上有Visual Studio .NET 2008, 即传说中的Visual Studio Codename Orcas的Beta2 Pre-release版本,虽然担心文件太大下不下来,但当时只有这一个办法了.还好,第二天都下完了.于是在Vista上安装好,把项目文件夹拷贝过来.
生成解决方案,通过. 调试,崩溃.
Debug Assertion Failed! 因为程序流程很简单,很快就发现哪里出错了. CDialog的SendMessage()函数好象不能用了(反正注释掉它就好了).
重新生成,通过;调试,通过;运行,成功.
因为程序小,所以改起来还比较容易.要是大了,想解这些BUG真的不容易.
把生成的程序拿到其他Vista机子上,想必应该可以运行了吧.没想到,又是一个对话框——
“The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.”
搜了搜,没搜到side-by-side configuration is incorrect的信息.很意外哦!难道我是第一个用在Vista里面写程序的菜鸟吗?怎么没有前辈给条线索?在MSDN上查side-by-side configuration,只是觉得又是一个什么工程配置之类的东西,结果没有该关键词.只看到了一个side-by-side application,跟进去看了一下.根据文章的描述和以往的经验判断,这篇文章就是说的就是我这个问题.继续跟进,发现一些新名词:
manifest
Manifests are XML files that accompany and describe side-by-side assemblies or isolated application. Manifests uniquely identify the assembly through the assembly’s <assemblyIdentity> element. They contain information used for building and activation, such as COM classes, interfaces, and type libraries, that has traditionally been stored in the registry. Manifests also specify the files that make the assembly and my include Windows classes if the assembly author wants them to be versioned. Side-by-side assemblies are not registered on the system, but are available to applications and other assemblies on the system that specify dependencies in manifest files.
side-by-side assemblies
A Windows side-by-side assembly is described by manifests. A side-by-side assembly contains a collection of resources – a group of DLLs, Windows classes, COM servers, type libraries, or interfaces – that are always provided to applications together.
Side-by-side assemblies are used by the operating system as fundamental units of naming, binding, versioning, deployment, and configuration. Every side-by-side assembly has a unique identity. One of the attributes of the assembly identity is its version. For more information, see Assembly Versions.
Starting with Windows XP, multiple versions of side-by-side assemblies can be used by applications running at the same time. Manifests, and the assembly version number, are used by the loader to determine the correct binding of assembly versions to applications. Side-by-side assemblies and manifests work with applications and the side-by-side manager as illustrated in the following figure.
isolated applications
Isolated applications are self-describing applications installed with manifests. Isolated applications can use both private assemblies and shared assemblies.
An application is considered fully isolated if all of its components are either shared side-by-side assemblies or private assemblies. It is called partially isolated if it uses some components that are not side-by-side assemblies. Note that if an application uses some components that are not side-by-side assemblies, or uses private assemblies, the application may be affected by the installation or removal of other applications on the system.
Developers are encouraged to design isolated applications and to update existing applications into isolated applications for the following reasons:
« Isolated applications are more stable and reliably updated because they are unaffected by the installation, removal, or upgrading of other applications on the system.
« Isolated applications can be designed so that they always run using the same assembly versions with which they were built and tested.
« Isolated applications can use functionality provided by the side-by-side assemblies made available by Microsoft. For more information, see Supported Microsoft Side-by-side Assemblies.
« Isolated applications are not tied to the shipping schedule of their side-by-side assemblies because applications and administrators can update the configuration after deployment without having to reinstall the application. This would not apply in the case where only one version of the assembly is being made available.
« A fully isolated application may be installed by using the xcopy command. Windows Installer can also be used to install an isolated application without impact to the registry. For more information, see Installation of Win32 Assemblies.
[返回] 中文XML论坛 - 专业的XML技术讨论区 →
计算机技术与应用 → 『 C/C++编程思想 』 → 用VC对VISTA编程笔记－1
(订阅本版)
2009/4/2 15:35:00
新浪微博
用VC对VISTA编程笔记－1