VB 2002和2003代码不兼容？ [英] VB 2002 and 2003 code incompatible?

问题描述

我家里有VB .net（2002年个人所有权），而我的

办公室（我们是MSDN开发商店）有.net 2003，我发现我不能写

代码回家，让它上班，再回到家里。这是因为2003年

转换了源代码。


我发现它的作用是将一些头文件更改为8.0版和

没有

更多因为我可以转换通过将8.0标签更换回来来回来




如果我将2002与第二版版本一起使用框架，和代码

是一样的，强制Gestapo像升级到每个版本的b / b
的意义是什么？


以防万一提出建议......我不会把2003年的工作带到家里安装

因为我确信它违反了MSDN许可证，

并且可能在全球范围内打破了几十条法律。


好​​的，所以你必须丢弃VB6中的代码并重新学习.net，但是这个<每10-15个月升级.net
将会变得昂贵。


问候，


Gary

I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we''re an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won''t bring 2003 from work
to install at home as I''m certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary

推荐答案

这两个版本使用不同版本的.NET Framework。一旦2002年

项目升级到2003项目，你就不能回去了。


Gary Napolitano < GN **** @ earthlink.net>在留言中写道

新闻：3F *************** @ earthlink.net ...

The 2 versions use different versions of the .NET Framework. Once a 2002
project has been upgraded to a 2003 project you can''t go back.

"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...

我有VB .net（ 2002年个人所有权）在家里，.net 2003在我的办公室（我们是MSDN开发商店），我发现我不能把代码写回家，带上班，然后回家再次。这是因为2003年转换了源代码。

我发现它的作用是将一些头文件更改为版本8.0并且没有更多
更多因为我可以转换通过将8.0标签更换回原来，如果我将2002与第二版版本一起使用。框架，和代码
是一样的，强迫Gestapo升级到每个版本的感觉是什么？

以防万一的建议是因为我确信它违反了MSDN许可证，并且可能在全球范围内打破了几十条法律，所以我不会把2003年从工作中带回来安装在家里。
>
好的，所以你必须丢弃VB6中的代码并重新学习.net，但每10-15个月升级一次.net会变得昂贵。
问候，

Gary

I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we''re an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won''t bring 2003 from work
to install at home as I''m certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary

有一些重大的代码更改。通过强制类似于gestapo的方式。战术，

微软将人们从自己身上拯救出来（即试图通过破坏旧IDE和轰炸中的
变化来运行代码）。


使用大部分代码，您只需更改XML并运行它。


通常，大多数1.0代码在1.1中运行而没有任何更改，这很好。


-

Gregory A. Beamer

MPV; MCP：+ I，SE，SD，DBA


**************************** ********************** ********************

在盒子外面思考！

************************************* ************* ********************

" Gary Napolitano" < GN **** @ earthlink.net>在留言中写道

新闻：3F *************** @ earthlink.net ...

There are some breaking code changes. By forcing the "gestapo-like" tactics,
Microsoft saves people from themselves (ie, trying to run code with breaking
changes in the older IDE and bombing).

With much of your code, you can simply change the XML and run it.

In general, most 1.0 code runs in 1.1 without any changes, which is good.

--
Gregory A. Beamer
MPV; MCP: +I, SE, SD, DBA

************************************************** ********************
Think outside the box!
************************************************** ********************
"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...

我有VB .net（ 2002年个人所有权）在家里，.net 2003在我的办公室（我们是MSDN开发商店），我发现我不能把代码写回家，带上班，然后回家再次。这是因为2003年转换了源代码。

我发现它的作用是将一些头文件更改为版本8.0并且没有更多
更多因为我可以转换通过将8.0标签更换回原来，如果我将2002与第二版版本一起使用。框架，和代码
是一样的，强迫Gestapo升级到每个版本的感觉是什么？

以防万一的建议是因为我确信它违反了MSDN许可证，并且可能在全球范围内打破了几十条法律，所以我不会把2003年从工作中带回来安装在家里。
>
好的，所以你必须丢弃VB6中的代码并重新学习.net，但每10-15个月升级一次.net会变得昂贵。
问候，

Gary

I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we''re an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won''t bring 2003 from work
to install at home as I''m certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary

将vs.net 2003项目转换为2002格式的免费工具。
http://www.thecodeproject.com/macro/...ert%7Cvs%2Enet


Ken

---------------------

" Gary Napolitano" < GN **** @ earthlink.net>在留言中写道

新闻：3F *************** @ earthlink.net ...

Hi,

A free utility to convert vs.net 2003 project to 2002 format.
http://www.thecodeproject.com/macro/...ert%7Cvs%2Enet

Ken
---------------------
"Gary Napolitano" <gn****@earthlink.net> wrote in message
news:3F***************@earthlink.net...

我有VB .net（ 2002年个人所有权）在家里，.net 2003在我的办公室（我们是MSDN开发商店），我发现我不能把代码写回家，带上班，然后回家再次。这是因为2003年转换了源代码。

我发现它的作用是将一些头文件更改为版本8.0并且没有更多
更多因为我可以转换通过将8.0标签更换回原来，如果我将2002与第二版版本一起使用。框架，和代码
是一样的，强迫Gestapo升级到每个版本的感觉是什么？

以防万一的建议是因为我确信它违反了MSDN许可证，并且可能在全球范围内打破了几十条法律，所以我不会把2003年从工作中带回来安装在家里。
>
好的，所以你必须丢弃VB6中的代码并重新学习.net，但每10-15个月升级一次.net会变得昂贵。
问候，

Gary

I have VB .net (2002 personal ownership) at home, and .net 2003 at my
office (we''re an MSDN developer shop) and I found that I cannot write
code home, bring it to work, and back home again. This is because 2003
"converts" the source code.

What I found it does is it changes some header files to version 8.0 and
nothing
more because I can "convert" it back by replacing the 8.0 label back to
7.0

If I use 2002 with the second "edition" of the framework, AND the code
was the same, what is the sense of forcing a Gestapo like upgrade to
every version that comes along?

Just in case the suggestion is made... I won''t bring 2003 from work
to install at home as I''m certain that it violates the MSDN license,
and probably breaks a few dozen laws worldwide.

OK, so you have to throw away code from VB6 and re-learn .net, but this
upgrading .net every 10-15 months is going to get expensive.

Regards,

Gary

这篇关于VB 2002和2003代码不兼容？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！