保持Visual Studio 6的任何理由？ [英] Any reason to keep Visual Studio 6 around?

问题描述

我正试图清理笔记本电脑上的空间。目前有Visual Studio 6

+ MSDN 98，和VS2003 +最近的MSDN。我保留了较旧的VS6由于

一些遗留的应用程序奇怪的代码在VS2003下编译时遇到问题

（长篇小说......我没写过代码，它必须与

作者的ActiveX模块链接。


无论如何，我想除了一些细节之外那个，VS 2003

可能会编译大部分遗留的VC ++代码。任何人都可以认为

有什么理由可以保留它吗？ （我正试图在

笔记本电脑驱动器上清空空间以加载VS 2005 beta 2）。

I''m trying to clear space on a laptop. Currently have Visual Studio 6
+ MSDN 98, AND VS2003 + recent MSDN. I had kept the older VS6 due to
some legacy apps with odd code that had trouble compiling under VS2003
(a long story...I didn''t write the code, and it has to link with the
author''s ActiveX modules).

Anyway, I''m thinking that aside from some details like that, VS 2003
will probably compile most of the legacy VC++ code. Can anyone think
of any reason to keep it around? (I''m trying to clear space on a
laptop drive to load VS 2005 beta 2).

推荐答案

你好_B！

Hallo _B!

我正在试图清理笔记本电脑上的空间。目前有Visual Studio 6
+ MSDN 98，和VS2003 +最近的MSDN。我保留了旧的VS6，原因是一些遗留的应用程序奇怪的代码在VS2003下编译时遇到了麻烦（很长一段时间......我没有编写代码，而且必须链接到
作者的ActiveX模块。

无论如何，我想除了这样的一些细节之外，VS 2003可能会编译大部分的旧版VC ++码。任何人都可以认为有任何理由保留它吗？ （我正试图在笔记本电脑驱动器上清空空间以加载VS 2005 beta 2。）

I''m trying to clear space on a laptop. Currently have Visual Studio 6
+ MSDN 98, AND VS2003 + recent MSDN. I had kept the older VS6 due to
some legacy apps with odd code that had trouble compiling under VS2003
(a long story...I didn''t write the code, and it has to link with the
author''s ActiveX modules).

Anyway, I''m thinking that aside from some details like that, VS 2003
will probably compile most of the legacy VC++ code. Can anyone think
of any reason to keep it around? (I''m trying to clear space on a
laptop drive to load VS 2005 beta 2).

VC6和VC7.1之间的差异是有时很棒，有时候你可以在没有警告的情况下编译代码并且它可以工作，但是有些代码需要进行大量的更改，特别是当你使用一些非常简单的模板时。


我们仍然使用VC6作为我们的遗留代码，我们不会移植它。

所有新产品都在VC.NET 2003中，我们将在2005年跳槽当

可用且不再测试时！


-

Martin Richter [MVP] WWJD

在C中我们必须编写自己的错误代码。在C ++中我们可以继承它们。

FAQ： http：// www .mpdvc.de

样品： http：// www。 codeguru.com http://www.codeproject.com

The differences betwen VC6 and VC7.1 are sometimes great, sometimes you
can compile code without a warning and it works, but some code need a
lot of changes specially when you used some templates that are so simple.

We still use VC6 for our legacy code and we will not port it.
All new products are in VC.NET 2003 and we will jump on 2005 when
available and no longer beta!

--
Martin Richter [MVP] WWJD
"In C we had to code our own bugs. In C++ we can inherit them."
FAQ : http://www.mpdvc.de
Samples: http://www.codeguru.com http://www.codeproject.com

你好_B！

Hallo _B!

我正在试图清理笔记本电脑上的空间。目前有Visual Studio 6
+ MSDN 98，和VS2003 +最近的MSDN。我保留了旧的VS6，原因是一些遗留的应用程序奇怪的代码在VS2003下编译时遇到了麻烦（很长一段时间......我没有编写代码，而且必须链接到
作者的ActiveX模块。

无论如何，我想除了这样的一些细节之外，VS 2003可能会编译大部分的旧版VC ++码。任何人都可以认为有任何理由保留它吗？ （我正试图在笔记本电脑驱动器上清空空间以加载VS 2005 beta 2。）

I''m trying to clear space on a laptop. Currently have Visual Studio 6
+ MSDN 98, AND VS2003 + recent MSDN. I had kept the older VS6 due to
some legacy apps with odd code that had trouble compiling under VS2003
(a long story...I didn''t write the code, and it has to link with the
author''s ActiveX modules).

Anyway, I''m thinking that aside from some details like that, VS 2003
will probably compile most of the legacy VC++ code. Can anyone think
of any reason to keep it around? (I''m trying to clear space on a
laptop drive to load VS 2005 beta 2).

VC6和VC7.1之间的差异是有时很棒，有时候你可以在没有警告的情况下编译代码并且它可以工作，但是有些代码需要进行大量的更改，特别是当你使用一些非常简单的模板时。


我们仍然使用VC6作为我们的遗留代码，我们不会移植它。

所有新产品都在VC.NET 2003中，我们将在2005年跳槽当

可用且不再测试时！


-

Martin Richter [MVP] WWJD

在C中我们必须编写自己的错误代码。在C ++中我们可以继承它们。

FAQ： http：// www .mpdvc.de

样品： http：// www。 codeguru.com http://www.codeproject.com

The differences betwen VC6 and VC7.1 are sometimes great, sometimes you
can compile code without a warning and it works, but some code need a
lot of changes specially when you used some templates that are so simple.

We still use VC6 for our legacy code and we will not port it.
All new products are in VC.NET 2003 and we will jump on 2005 when
available and no longer beta!

--
Martin Richter [MVP] WWJD
"In C we had to code our own bugs. In C++ we can inherit them."
FAQ : http://www.mpdvc.de
Samples: http://www.codeguru.com http://www.codeproject.com

On Tue，2005年7月5日10:55:13 +0200，Martin Richter [MVP]

< ma ***** *******@mvps.org>写道：

On Tue, 05 Jul 2005 10:55:13 +0200, "Martin Richter [MVP]"
<ma************@mvps.org> wrote:

你好_B！

Hallo _B!

我正试图清理笔记本电脑上的空间。目前有Visual Studio 6
+ MSDN 98，和VS2003 +最近的MSDN。我保留了旧的VS6，原因是一些遗留的应用程序奇怪的代码在VS2003下编译时遇到了麻烦（很长一段时间......我没有编写代码，而且必须链接到
作者的ActiveX模块。

无论如何，我想除了这样的一些细节之外，VS 2003可能会编译大部分的旧版VC ++码。任何人都可以认为有任何理由保留它吗？ （我正试图在笔记本电脑驱动器上清空空间以加载VS 2005 beta 2）。
VC6和VC7.1之间的差异有时很大，有时候你可以编译代码没有警告就可以了，但有些代码需要进行大量更改，特别是当你使用一些非常简单的模板时。

I''m trying to clear space on a laptop. Currently have Visual Studio 6
+ MSDN 98, AND VS2003 + recent MSDN. I had kept the older VS6 due to
some legacy apps with odd code that had trouble compiling under VS2003
(a long story...I didn''t write the code, and it has to link with the
author''s ActiveX modules).

Anyway, I''m thinking that aside from some details like that, VS 2003
will probably compile most of the legacy VC++ code. Can anyone think
of any reason to keep it around? (I''m trying to clear space on a
laptop drive to load VS 2005 beta 2).
The differences betwen VC6 and VC7.1 are sometimes great, sometimes you
can compile code without a warning and it works, but some code need a
lot of changes specially when you used some templates that are so simple.

我害怕你我会这么说的。是的，我自己的大部分代码

将在2003年编译而没有太大问题，我最近一直在编写

。所以我希望能够使用VS.NET 2003.


AND ...我想在C ++ / CLI上加快速度，这意味着加载VS

2005测试版2.


和...相关的MSDN。


总而言之，大量的磁盘空间。我在开发站有空间，

但不在笔记本电脑上。我无法解决我可以为了测试2005测试版2而花费多少资金。

我们仍然使用VC6作为我们的遗留代码，我们不会移植它。
所有新产品都在VC.NET 2003中，我们将在2005年推出
并且不再测试！

I was afraid you were going to say that. Yeah, most of my own code
willl compile under 2003 without much problem, and I''ve been writing
mostly C# lately. So I was hoping to get by with VS.NET 2003.

AND...I want to get up to speed on C++/CLI, which means loading VS
2005 beta 2.

And...associated MSDNs.

All in all, LOTs of disk space. I have room on the devel stations,
but not on the laptop. I''m having trouble puzzling out what I can
erase to make space for 2005 beta 2.
We still use VC6 for our legacy code and we will not port it.
All new products are in VC.NET 2003 and we will jump on 2005 when
available and no longer beta!

如果2005年发布我可能只是放弃VS 2003，但

我不确定2005 beta2的稳定程度如何 - 任何人的意见？

If 2005 release was available I could probably just ditch VS 2003, but
I''m not sure how stable 2005 beta2 is -- any opinions from anyone?

这篇关于保持Visual Studio 6的任何理由？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！