Yes, I know... I could set up a virtual machine running XP. Unfortunately our build environment is such that we need to be running VC2003, 2005 and 2008 concurrently and it would be much more convenient if I could run 2003 natively on Windows 7 for the few projects we have that require it.
是的,我知道......我可以设置运行XP的虚拟机。不幸的是,我们的构建环境需要同时运行VC2003,2005和2008,如果我可以在Windows 7上本机运行2003我们需要它的少数项目,这将更加方便。
I realize some things may not be available in the IDE, but I was able to run 2003 under windows Vista and if I could get the same base level of functionality under Windows 7 I would be extremely happy.
我意识到IDE中可能没有一些东西可用,但我能够在Windows Vista下运行2003,如果我能在Windows 7下获得相同的基本功能,我会非常高兴。
Right now I get an error opening the *.pdb file when I compile after switching vc2003 to run as Administrator under compatibility mode for XP SP 2.
现在,当我在切换vc2003以在XP SP 2的兼容模式下以管理员身份运行后编译时,打开* .pdb文件时出错。
Thanks!
15 个解决方案
#1
Give XP Mode a try if you can't get it to run natively.
如果你不能让它本机运行,试试XP Mode。
#2
I wrote a blog entry about this a while back that you can check out - http://technikhil.wordpress.com/2010/01/12/visual-studio-2003-and-windows-7-can-get-along-really/
我写了一篇关于这篇文章的博客文章,你可以看看 - http://technikhil.wordpress.com/2010/01/12/visual-studio-2003-and-windows-7-can-get-along-真/
The only thing I am stuck on right now is the global search functionality of VS 2003 - it hangs the application. My workaround is to use windows 7 search :-). Other than that - so far so good...
我现在唯一困住的是VS 2003的全局搜索功能 - 它挂起了应用程序。我的解决方法是使用Windows 7搜索:-)。除此之外 - 到目前为止一切都很好......
Update: I got the search to work as well by disabling the Aero functionality - I have updated my blog post with the details...
更新:我通过禁用Aero功能使搜索工作正常 - 我已经更新了我的博客帖子,其中包含详细信息......
#3
(Much of this repeats what's already been written above.)
(其中大部分重复了上面已经写过的内容。)
I need to run VS2003 as adminstrator under Win7 64-bit, to support legacy projects (e.g. those that run on the original Xbox). The old XDK requires VS2003, so upgrading is not an option. I could run WinXP but I prefer Win7.
我需要在Win7 64位下运行VS2003作为管理员,以支持遗留项目(例如在原始Xbox上运行的项目)。旧的XDK需要VS2003,因此升级不是一种选择。我可以运行WinXP,但我更喜欢Win7。
VS2003 is not officially supported under Win7 and trying to do so creates a couple of fairly annoying problems:
Win7下没有正式支持VS2003,并试图这样做会产生一些相当恼人的问题:
Find-in-files causes VS2003 to hang. Linking fails due to a PDB file handle leak. The Find-in-files hang is solved by using "Disable visual themes". Navigate to the VS2003 shortcut (Start-->Microsoft Visual Studio .NET 2003), right-click to get context menu, select Compatibility tab, Settings pane, and check "Disable visual themes".
Find-in-files导致VS2003挂起。由于PDB文件句柄泄漏,链接失败。使用“禁用可视主题”解决了“在文件中查找”的问题。导航到VS2003快捷方式(“开始” - >“Microsoft Visual Studio .NET 2003”),右键单击以获取上下文菜单,选择“兼容性”选项卡,“设置”窗格,然后选中“禁用可视主题”。
The linker failure (LNK1201) happens when you run the program through the debugger, stop it, modify a file and build. The error is that a Visual Studio hold a handle to the PDB file, while the linker tries to write to that file. You can stop and restart VS2003 to bypass the issue. Works but is annoying.
通过调试器运行程序,停止它,修改文件和构建时,会发生链接器故障(LNK1201)。错误是Visual Studio保存PDB文件的句柄,而链接器尝试写入该文件。您可以停止并重新启动VS2003以绕过该问题。工作,但很烦人。
You can also use the Microsoft SysInternals "handle.exe" utility to find, then close handles held by a process on a particular file. Write a script to call handle.exe and set up the VS2003 project to run that script as a Pre-Build Event. (See this thread.) But handle.exe requires running as admin.
您还可以使用Microsoft SysInternals“handle.exe”实用程序来查找,然后关闭特定文件上进程持有的句柄。编写脚本来调用handle.exe并设置VS2003项目以将该脚本作为预构建事件运行。 (请参阅此主题。)但handle.exe需要以管理员身份运行。
You could hypothetically change handle.exe to run as admin using the usual steps (e.g. as a compatibility setting) but then handle.exe (apparently) runs in a nested shell, and then the stdout text does not get to the calling script.
您可以假设将handle.exe更改为使用常规步骤(例如作为兼容性设置)以管理员身份运行,但随后handle.exe(显然)在嵌套shell中运行,然后stdout文本无法访问调用脚本。
You can make VS2003 run as admin, in which case the Pre-Build script also runs as admin, hence does handle.exe, and that works.
您可以使VS2003以管理员身份运行,在这种情况下,预构建脚本也以管理员身份运行,因此执行handle.exe,这样可行。
The remaining trick is to get VS2003 SLN files to open properly. If you simply make VS2003 run as admin automatically then the VS version selector fails to run VS2003. I don't know why, but it is the case.
剩下的技巧是让VS2003 SLN文件正常打开。如果您只是让VS2003自动以管理员身份运行,那么VS版本选择器无法运行VS2003。我不知道为什么,但情况确实如此。
You could associate SLN files to open using VS2003 devenv.exe instead of VSLauncher.exe. That works but then all new SLN files (2005, 2008, 2010, 2012, ...) fail to open.
您可以使用VS2003 devenv.exe而不是VSLauncher.exe将SLN文件关联。这可行,但所有新的SLN文件(2005年,2008年,2010年,2012年,...)都无法打开。
So the final step then is to make VSLauncher.exe run as admin. This fails as of KB2492386 as this thread indicates. Uninstalling that update was the final step in this saga, to get everything to work.
因此,最后一步是使VSLauncher.exe以管理员身份运行。从此线程指示的KB2492386失败。卸载该更新是这个问题的最后一步,让一切工作正常。
#4
Run this install. You need to run it from the setup directory, the setup.exe on the root of the cd will not work.
运行此安装。您需要从安装目录运行它,CD根目录下的setup.exe将无法正常工作。
D:\setup\SetUp.exe /NO_BSLN_CHECK
#5
PATCH NOW AVAILABLE
After some reverse-engineering, I found the incorrectly refcounted COM object responsible for the leak (it was off by 1) and developed a stable patch and corresponding article describing the fix. This addresses problems encountered while using Windows 7 thru Windows 10. Details and download available at:
现在可用的补丁经过一些逆向工程后,我发现错误的refcounted COM对象负责泄漏(它被1关闭)并开发了一个稳定的补丁和相应的文章来描述修复。这解决了使用Windows 7到Windows 10时遇到的问题。详细信息和下载位于:
http://bytepointer.com/articles/vs7.1_2003_on_win7_pdb_handle_leak_bug_unofficial_fix.htm
If you want to perform the patch manually, those details are also included.
如果要手动执行修补程序,还会包括这些详细信息。
NOTE: The SysInternals Handle tool workaround did not work for files on a network-share. The .PDB was not completely unlocked although the Handle tool claimed it was closed. My fix eliminates the problem once and for all and avoids any side effects.
注意:SysInternals Handle工具解决方法不适用于网络共享上的文件。虽然Handle工具声称它已关闭,但.PDB并未完全解锁。我的修复一劳永逸地消除了这个问题,避免了任何副作用。
#6
Solution i found on the web which helped: For your visual studio, use application compatibility = windows vista SP2, and NOT WinXP SP3
我在网上找到的解决方案有助于:对于您的visual studio,使用应用程序兼容性= windows vista SP2,而不是WinXP SP3
#7
I have a really dirty and pathetic workaround for the pdb problem.
对于pdb问题,我有一个非常肮脏和可怜的解决方法。
Download and run Sysinternals-ProceXP, press CTRL-F enter the name of pdb(smt like ($ProjectName).pdb) that can't be created while linking. Double click when it is found.(if it can't be found run procexp with administrator priviliges)
下载并运行Sysinternals-ProceXP,按CTRL-F输入链接时无法创建的pdb(smt like($ ProjectName).pdb)的名称。找到它时双击。(如果找不到,请使用管理员权限运行procexp)
Then you will see that the .pdb file is highlighted in the lower pane of the main screen. Right click it and select Close Handle. When you retry building your solution it wont raise an error.
然后您将看到.pdb文件在主屏幕的下部窗格中突出显示。右键单击它并选择Close Handle。当您重试构建解决方案时,它不会引发错误。
I dont know if this solution can be scripted but it is at least better than restarting visual studio.
我不知道这个解决方案是否可以编写脚本,但它至少比重启visual studio更好。
#8
I've been using Visual studio 2003 on win7 since the very first RC edition was released :S why do people have issues?
自从第一个RC版本发布以来,我一直在win7上使用Visual Studio 2003:为什么人们有问题?
#9
I have attempted to install VS2003 on Windows 7 64-bit using the Virtual Windows XP feature. I'm reasonably certain that this will be successful. The issue I ran into is that the installer wants IIS installed, and the XP installation provided by the Virtual XP doesn't have that enabled by default.
我试图使用Virtual Windows XP功能在Windows 7 64位上安装VS2003。我有理由相信这会成功。我遇到的问题是安装程序需要安装IIS,而Virtual XP提供的XP安装默认情况下没有启用。
If you go to Add/Remove components, and try to add it, it will ask for the disc, which I didn't have on hand. Once I get my hands on the disc, I'm pretty sure that it will run fine.
如果你去添加/删除组件,并尝试添加它,它将要求光盘,我手头没有。一旦我把手放在光盘上,我很确定它能正常运行。
If you haven't tried it for other apps, the Virtual XP feature is really neat...
如果您还没有尝试过其他应用程序,那么Virtual XP功能真的很整洁......
#10
I am experiencing the same issue; devenv.exe is leaving pdb files open after running the project. I have made a batch file to work around it, it closes all .pdb files open by devenv.exe:
我遇到了同样的问题; devenv.exe在运行项目后打开pdb文件。我已经制作了一个批处理文件来解决它,它会关闭devenv.exe打开的所有.pdb文件:
handle.exe .pdb | awk "/devenv.exe/ { split($4, fd, \":\"); system(\"handle.exe -c \" fd[1] \" -y -p \" $3)}"
handle.exe .pdb | awk“/devenv.exe/ {split($ 4,fd,\”:\“); system(\”handle.exe -c \“fd [1] \” - y -p \“$ 3)}”
You will need to have handle.exe by sysinternals and awk by gnu in your path to make it work.
您将需要sysinternals中的handle.exe和路径中的gnu awk才能使其工作。
Use at your own risk. Closing handles can cause application or system instability.
使用风险由您自己承担。关闭句柄可能导致应用程序或系统不稳定。
#11
In windows 7, there is the compatabiliy mode in the executable properties. open:C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\ then right click on the devenv.exe and select properties. In the compatability tab, select the "Run in compatability mode" and select "Windows XP" in the dropdown.
在Windows 7中,可执行属性中存在兼容模式。打开:C:\ Program Files \ Microsoft Visual Studio .NET 2003 \ Common7 \ IDE \然后右键单击devenv.exe并选择属性。在兼容性选项卡中,选择“在兼容模式下运行”,然后在下拉列表中选择“Windows XP”。
Try that, I am not sure if it works, but it is worth a shot.
试试看,我不确定它是否有效,但值得一试。
#12
I am having no problems with Visual Studio 2003 on Windows 7 64-bit.
我对Windows 7 64位上的Visual Studio 2003没有任何问题。
- Navigate to VS2003 devenv.exe (probably C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe)
- Right-click and select Properties
- In the Compatibility tab, check "Run this program in compatibility mode for:" and select "Windows XP (Service Pack 3)"
- Check "Run this program as administrator"
导航到VS2003 devenv.exe(可能是C:\ Program Files(x86)\ Microsoft Visual Studio .NET 2003 \ Common7 \ IDE \ devenv.exe)
右键单击并选择“属性”
在兼容性选项卡中,选中“在兼容模式下运行此程序:”并选择“Windows XP(Service Pack 3)”
选中“以管理员身份运行此程序”
#13
I got Visual Studio .NET 2003 Working just fine on my HP EliteBook Workstation 8760W with an I7 processor and 12GB of RAM running Windows 7 Professional 64 bit by doing some advanced steps. They go as follows:
我使用I7处理器和运行Windows 7 Professional 64位的12GB RAM,通过一些高级步骤,在我的HP EliteBook工作站8760W上运行Visual Studio .NET 2003。它们如下:
- Install FrontPage 2002 Server Extensions for IIS 7.0.
- Install Visual Studio .Net 2003. Just skip when the installer command you to configure Frontpage 2002 Server Extensions.
- Install .Net Framework 1.1 Service Pack 1 (download here).
- Go to Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. Highlight your machine, then double-click on ISAPI and CGI Restrictions. Change setting for ASP .NET v1.1.4322 to Allowed.
安装IIS 7.0的FrontPage 2002 Server Extensions。
安装Visual Studio .Net 2003.只需在安装程序命令您配置Frontpage 2002 Server Extensions时跳过。
安装.Net Framework 1.1 Service Pack 1(在此处下载)。
转到“控制面板”>“管理工具”>“Internet信息服务(IIS)管理器”。突出显示您的计算机,然后双击ISAPI和CGI限制。将ASP .NET v1.1.4322的设置更改为“允许”。
Then it will always show an alert with the following message
然后它将始终显示带有以下消息的警报
This program has compatibility issues...
该程序存在兼容性问题......
just ignore that. Also, don't put it in compatibility mode in the properties of the IDE.
只是忽略它。另外,请勿在IDE的属性中将其置于兼容模式。
#14
I'm sorry, your build environment requires you to have VC 2003, 2005, AND 2008 running concurrently? I would really bet that your efforts would be better spent simply consolidating your build environment to just one environment.
对不起,您的构建环境要求您同时运行VC 2003,2005和2008?我真的敢打赌,只需将构建环境整合到一个环境中,您的努力就会更好。
#15
Have you considered upgrading your solutions to vs2005, using MSBEE to target .net 1.1?
你有没有考虑过将你的解决方案升级到vs2005,使用MSBEE来定位.net 1.1?
#1
Give XP Mode a try if you can't get it to run natively.
如果你不能让它本机运行,试试XP Mode。
#2
I wrote a blog entry about this a while back that you can check out - http://technikhil.wordpress.com/2010/01/12/visual-studio-2003-and-windows-7-can-get-along-really/
我写了一篇关于这篇文章的博客文章,你可以看看 - http://technikhil.wordpress.com/2010/01/12/visual-studio-2003-and-windows-7-can-get-along-真/
The only thing I am stuck on right now is the global search functionality of VS 2003 - it hangs the application. My workaround is to use windows 7 search :-). Other than that - so far so good...
我现在唯一困住的是VS 2003的全局搜索功能 - 它挂起了应用程序。我的解决方法是使用Windows 7搜索:-)。除此之外 - 到目前为止一切都很好......
Update: I got the search to work as well by disabling the Aero functionality - I have updated my blog post with the details...
更新:我通过禁用Aero功能使搜索工作正常 - 我已经更新了我的博客帖子,其中包含详细信息......
#3
(Much of this repeats what's already been written above.)
(其中大部分重复了上面已经写过的内容。)
I need to run VS2003 as adminstrator under Win7 64-bit, to support legacy projects (e.g. those that run on the original Xbox). The old XDK requires VS2003, so upgrading is not an option. I could run WinXP but I prefer Win7.
我需要在Win7 64位下运行VS2003作为管理员,以支持遗留项目(例如在原始Xbox上运行的项目)。旧的XDK需要VS2003,因此升级不是一种选择。我可以运行WinXP,但我更喜欢Win7。
VS2003 is not officially supported under Win7 and trying to do so creates a couple of fairly annoying problems:
Win7下没有正式支持VS2003,并试图这样做会产生一些相当恼人的问题:
Find-in-files causes VS2003 to hang. Linking fails due to a PDB file handle leak. The Find-in-files hang is solved by using "Disable visual themes". Navigate to the VS2003 shortcut (Start-->Microsoft Visual Studio .NET 2003), right-click to get context menu, select Compatibility tab, Settings pane, and check "Disable visual themes".
Find-in-files导致VS2003挂起。由于PDB文件句柄泄漏,链接失败。使用“禁用可视主题”解决了“在文件中查找”的问题。导航到VS2003快捷方式(“开始” - >“Microsoft Visual Studio .NET 2003”),右键单击以获取上下文菜单,选择“兼容性”选项卡,“设置”窗格,然后选中“禁用可视主题”。
The linker failure (LNK1201) happens when you run the program through the debugger, stop it, modify a file and build. The error is that a Visual Studio hold a handle to the PDB file, while the linker tries to write to that file. You can stop and restart VS2003 to bypass the issue. Works but is annoying.
通过调试器运行程序,停止它,修改文件和构建时,会发生链接器故障(LNK1201)。错误是Visual Studio保存PDB文件的句柄,而链接器尝试写入该文件。您可以停止并重新启动VS2003以绕过该问题。工作,但很烦人。
You can also use the Microsoft SysInternals "handle.exe" utility to find, then close handles held by a process on a particular file. Write a script to call handle.exe and set up the VS2003 project to run that script as a Pre-Build Event. (See this thread.) But handle.exe requires running as admin.
您还可以使用Microsoft SysInternals“handle.exe”实用程序来查找,然后关闭特定文件上进程持有的句柄。编写脚本来调用handle.exe并设置VS2003项目以将该脚本作为预构建事件运行。 (请参阅此主题。)但handle.exe需要以管理员身份运行。
You could hypothetically change handle.exe to run as admin using the usual steps (e.g. as a compatibility setting) but then handle.exe (apparently) runs in a nested shell, and then the stdout text does not get to the calling script.
您可以假设将handle.exe更改为使用常规步骤(例如作为兼容性设置)以管理员身份运行,但随后handle.exe(显然)在嵌套shell中运行,然后stdout文本无法访问调用脚本。
You can make VS2003 run as admin, in which case the Pre-Build script also runs as admin, hence does handle.exe, and that works.
您可以使VS2003以管理员身份运行,在这种情况下,预构建脚本也以管理员身份运行,因此执行handle.exe,这样可行。
The remaining trick is to get VS2003 SLN files to open properly. If you simply make VS2003 run as admin automatically then the VS version selector fails to run VS2003. I don't know why, but it is the case.
剩下的技巧是让VS2003 SLN文件正常打开。如果您只是让VS2003自动以管理员身份运行,那么VS版本选择器无法运行VS2003。我不知道为什么,但情况确实如此。
You could associate SLN files to open using VS2003 devenv.exe instead of VSLauncher.exe. That works but then all new SLN files (2005, 2008, 2010, 2012, ...) fail to open.
您可以使用VS2003 devenv.exe而不是VSLauncher.exe将SLN文件关联。这可行,但所有新的SLN文件(2005年,2008年,2010年,2012年,...)都无法打开。
So the final step then is to make VSLauncher.exe run as admin. This fails as of KB2492386 as this thread indicates. Uninstalling that update was the final step in this saga, to get everything to work.
因此,最后一步是使VSLauncher.exe以管理员身份运行。从此线程指示的KB2492386失败。卸载该更新是这个问题的最后一步,让一切工作正常。
#4
Run this install. You need to run it from the setup directory, the setup.exe on the root of the cd will not work.
运行此安装。您需要从安装目录运行它,CD根目录下的setup.exe将无法正常工作。
D:\setup\SetUp.exe /NO_BSLN_CHECK
#5
PATCH NOW AVAILABLE
After some reverse-engineering, I found the incorrectly refcounted COM object responsible for the leak (it was off by 1) and developed a stable patch and corresponding article describing the fix. This addresses problems encountered while using Windows 7 thru Windows 10. Details and download available at:
现在可用的补丁经过一些逆向工程后,我发现错误的refcounted COM对象负责泄漏(它被1关闭)并开发了一个稳定的补丁和相应的文章来描述修复。这解决了使用Windows 7到Windows 10时遇到的问题。详细信息和下载位于:
http://bytepointer.com/articles/vs7.1_2003_on_win7_pdb_handle_leak_bug_unofficial_fix.htm
If you want to perform the patch manually, those details are also included.
如果要手动执行修补程序,还会包括这些详细信息。
NOTE: The SysInternals Handle tool workaround did not work for files on a network-share. The .PDB was not completely unlocked although the Handle tool claimed it was closed. My fix eliminates the problem once and for all and avoids any side effects.
注意:SysInternals Handle工具解决方法不适用于网络共享上的文件。虽然Handle工具声称它已关闭,但.PDB并未完全解锁。我的修复一劳永逸地消除了这个问题,避免了任何副作用。
#6
Solution i found on the web which helped: For your visual studio, use application compatibility = windows vista SP2, and NOT WinXP SP3
我在网上找到的解决方案有助于:对于您的visual studio,使用应用程序兼容性= windows vista SP2,而不是WinXP SP3
#7
I have a really dirty and pathetic workaround for the pdb problem.
对于pdb问题,我有一个非常肮脏和可怜的解决方法。
Download and run Sysinternals-ProceXP, press CTRL-F enter the name of pdb(smt like ($ProjectName).pdb) that can't be created while linking. Double click when it is found.(if it can't be found run procexp with administrator priviliges)
下载并运行Sysinternals-ProceXP,按CTRL-F输入链接时无法创建的pdb(smt like($ ProjectName).pdb)的名称。找到它时双击。(如果找不到,请使用管理员权限运行procexp)
Then you will see that the .pdb file is highlighted in the lower pane of the main screen. Right click it and select Close Handle. When you retry building your solution it wont raise an error.
然后您将看到.pdb文件在主屏幕的下部窗格中突出显示。右键单击它并选择Close Handle。当您重试构建解决方案时,它不会引发错误。
I dont know if this solution can be scripted but it is at least better than restarting visual studio.
我不知道这个解决方案是否可以编写脚本,但它至少比重启visual studio更好。
#8
I've been using Visual studio 2003 on win7 since the very first RC edition was released :S why do people have issues?
自从第一个RC版本发布以来,我一直在win7上使用Visual Studio 2003:为什么人们有问题?
#9
I have attempted to install VS2003 on Windows 7 64-bit using the Virtual Windows XP feature. I'm reasonably certain that this will be successful. The issue I ran into is that the installer wants IIS installed, and the XP installation provided by the Virtual XP doesn't have that enabled by default.
我试图使用Virtual Windows XP功能在Windows 7 64位上安装VS2003。我有理由相信这会成功。我遇到的问题是安装程序需要安装IIS,而Virtual XP提供的XP安装默认情况下没有启用。
If you go to Add/Remove components, and try to add it, it will ask for the disc, which I didn't have on hand. Once I get my hands on the disc, I'm pretty sure that it will run fine.
如果你去添加/删除组件,并尝试添加它,它将要求光盘,我手头没有。一旦我把手放在光盘上,我很确定它能正常运行。
If you haven't tried it for other apps, the Virtual XP feature is really neat...
如果您还没有尝试过其他应用程序,那么Virtual XP功能真的很整洁......
#10
I am experiencing the same issue; devenv.exe is leaving pdb files open after running the project. I have made a batch file to work around it, it closes all .pdb files open by devenv.exe:
我遇到了同样的问题; devenv.exe在运行项目后打开pdb文件。我已经制作了一个批处理文件来解决它,它会关闭devenv.exe打开的所有.pdb文件:
handle.exe .pdb | awk "/devenv.exe/ { split($4, fd, \":\"); system(\"handle.exe -c \" fd[1] \" -y -p \" $3)}"
handle.exe .pdb | awk“/devenv.exe/ {split($ 4,fd,\”:\“); system(\”handle.exe -c \“fd [1] \” - y -p \“$ 3)}”
You will need to have handle.exe by sysinternals and awk by gnu in your path to make it work.
您将需要sysinternals中的handle.exe和路径中的gnu awk才能使其工作。
Use at your own risk. Closing handles can cause application or system instability.
使用风险由您自己承担。关闭句柄可能导致应用程序或系统不稳定。
#11
In windows 7, there is the compatabiliy mode in the executable properties. open:C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\ then right click on the devenv.exe and select properties. In the compatability tab, select the "Run in compatability mode" and select "Windows XP" in the dropdown.
在Windows 7中,可执行属性中存在兼容模式。打开:C:\ Program Files \ Microsoft Visual Studio .NET 2003 \ Common7 \ IDE \然后右键单击devenv.exe并选择属性。在兼容性选项卡中,选择“在兼容模式下运行”,然后在下拉列表中选择“Windows XP”。
Try that, I am not sure if it works, but it is worth a shot.
试试看,我不确定它是否有效,但值得一试。
#12
I am having no problems with Visual Studio 2003 on Windows 7 64-bit.
我对Windows 7 64位上的Visual Studio 2003没有任何问题。
- Navigate to VS2003 devenv.exe (probably C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe)
- Right-click and select Properties
- In the Compatibility tab, check "Run this program in compatibility mode for:" and select "Windows XP (Service Pack 3)"
- Check "Run this program as administrator"
导航到VS2003 devenv.exe(可能是C:\ Program Files(x86)\ Microsoft Visual Studio .NET 2003 \ Common7 \ IDE \ devenv.exe)
右键单击并选择“属性”
在兼容性选项卡中,选中“在兼容模式下运行此程序:”并选择“Windows XP(Service Pack 3)”
选中“以管理员身份运行此程序”
#13
I got Visual Studio .NET 2003 Working just fine on my HP EliteBook Workstation 8760W with an I7 processor and 12GB of RAM running Windows 7 Professional 64 bit by doing some advanced steps. They go as follows:
我使用I7处理器和运行Windows 7 Professional 64位的12GB RAM,通过一些高级步骤,在我的HP EliteBook工作站8760W上运行Visual Studio .NET 2003。它们如下:
- Install FrontPage 2002 Server Extensions for IIS 7.0.
- Install Visual Studio .Net 2003. Just skip when the installer command you to configure Frontpage 2002 Server Extensions.
- Install .Net Framework 1.1 Service Pack 1 (download here).
- Go to Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. Highlight your machine, then double-click on ISAPI and CGI Restrictions. Change setting for ASP .NET v1.1.4322 to Allowed.
安装IIS 7.0的FrontPage 2002 Server Extensions。
安装Visual Studio .Net 2003.只需在安装程序命令您配置Frontpage 2002 Server Extensions时跳过。
安装.Net Framework 1.1 Service Pack 1(在此处下载)。
转到“控制面板”>“管理工具”>“Internet信息服务(IIS)管理器”。突出显示您的计算机,然后双击ISAPI和CGI限制。将ASP .NET v1.1.4322的设置更改为“允许”。
Then it will always show an alert with the following message
然后它将始终显示带有以下消息的警报
This program has compatibility issues...
该程序存在兼容性问题......
just ignore that. Also, don't put it in compatibility mode in the properties of the IDE.
只是忽略它。另外,请勿在IDE的属性中将其置于兼容模式。
#14
I'm sorry, your build environment requires you to have VC 2003, 2005, AND 2008 running concurrently? I would really bet that your efforts would be better spent simply consolidating your build environment to just one environment.
对不起,您的构建环境要求您同时运行VC 2003,2005和2008?我真的敢打赌,只需将构建环境整合到一个环境中,您的努力就会更好。
#15
Have you considered upgrading your solutions to vs2005, using MSBEE to target .net 1.1?
你有没有考虑过将你的解决方案升级到vs2005,使用MSBEE来定位.net 1.1?