微软MVP说他们想要老VB回来 [英] Microsoft MVPs Say They Want Old VB Back

问题描述

http://www.eweek.com /article2/0,1759,1774642,00.asp

推荐答案

嗨Jim，


Jim Hubbard <再*** @ groups.please> schrieb：

Hi Jim,

"Jim Hubbard" <re***@groups.please> schrieb:

http： //www.eweek.com/article2/0,1759,1774642,00.asp

对于有兴趣签署请愿书的人：


关于请愿的一般信息（新闻，博客文章等）：

http://classicvb.org/


签名清单：

http://classicvb.org/petition/


-

MS Herfried K. Wagner

MVP< URL：http：//dotnet.mvps.org/>

VB< URL ：http：//classicvb.org/petition/>

For those who are interested in signing the petition:

General information (press, blog articles, etc.) about the petition:

http://classicvb.org/

List of signatures:

http://classicvb.org/petition/

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

肥皂盒时间!!!!!!!!


我无法理解，在2005年4月1日及之后，我不会怎样用VB6（SP6）来做我能做的事情。在2005年3月31日之前。

仅仅因为''主流'支持从该日期撤回并不意味着

我无法使用它。


请愿书的目标1谈到保护资产。如果你有一个资产，那么它现在已经存在了。如果今天有效，那么4月1日就不会停止工作了。因此，假设未来版本的VB6 / VBA（原文如此）（在此阶段，那里没有
不会是）会破坏你的资产。这就像是说无论将来开发的汽车型号是什么？b

总是必须为我特定车型提供支持今天开车。

换句话说 - ''我想看到创新，但我也想要一直以来的所有方式。'


在目标2中，它表示''这个核心应该被增强和扩展，并且

的变化应该遵循文件化的弃用过程。''我是唯一一个

谁想知道如何增强和扩展某些东西并在同一时间以
的价格扩大它。对我来说''增强和扩展''和''弃用''是完整的

对立面。


在目标3中它陈述''的决定，如何以及何时将代码迁移到.NET中的代码应该由客户承担。有些人可能选择继续使用

非托管VB，特别是对于遗留代码库。有些人只会使用VB.NET，

其他人混合使用。''请原谅我的错误，认为这正是今天的

案例并且不会改变4月1日。另外，不要忘记使用VB6，VB.NET和C＃.NET混合提供

解决方案的开发人员。


根据我的个人经验，我在VB6中只遇到了2个''问题'，需要由Microsoft解决，而且两个问题都在以后的服务包中解决。

与此同时，一个相当没有吸引力的解决方法被用来实现

期望的结果。虽然当时牙齿咬牙切齿，但痛苦很快就过去了。它确实提出了一个问题：'人们尝试用VB6做什么新事物？这些问题引起了如此众多的广泛问题，这仍然需要主流支持？''我很快就会认为

有些人正试图用VB6来做一些它本来不是为了b $ b做的事情，然后批评微软什么时候没有做到了。如果是这样的话，那么我恐怕不能支持这种行为。我也想知道是否有些人已经使用主流支持作为阅读

火焰手册或其他自助支持方法的替代方案 - 它肯定会出现

许多人以这种方式使用这些新组。


在一些关于此请愿的文章中，它讨论的项目不是

被迁移到VB.Net因为它很复杂。所以呢。与自行车相比，汽车是复杂的，但这并不能阻止青少年从自行车转移到汽车上。复杂并不意味着难!!!不幸的是，

是那些将这两个词等同起来的人，在这样做的时候，除了
之外什么都不会让他们感到困难。还有一些人似乎无法做任何事情，除非整个地方交给他们

在盘子上。除了这些之外，还有那些绞尽脑汁并且让他们自己生病的人，如果他们没有得到特定的代码，那么这是第一次正确的。对于所有那些我能说的帽子适合的人来说，

得到你的背后，为自己学点东西，准备好尝试一些东西。你会感到惊讶的是，当一个人没有花费精力等待其他人为一个人做这件事时，他们可以做多少。

如果一个人担心的话第一次就做对了。


为了完成，我相信微软在2年前宣布结束

主流支持VB6的时间表，所以我我也想知道为什么它会花费这么长时间才能出现这样的请愿书，或者说它没有什么比这对最近的一个下意识的反应更多提醒。


Stephany


" Herfried K. Wagner [MVP]" <喜*************** @ gmx.at>在消息中写道

新闻：Ot ************* @ TK2MSFTNGP15.phx.gbl ...

Soapbox time!!!!!!!!

I cannot understand how, on and after 1 April 2005, I am not going to be
able to do things with VB6(SP6) that I can do on and prior to 31 March 2005.
Just because ''Mainstream'' support is withdrawn from that date does not mean
I won''t be able to use it.

Objective 1 of the petition talks about ''Preservation of assets''. If you
have an asset then it is in place today. If it works today then it is not
magically going to stop working on 1 April. It is therefore spurious to
argue that a ''Future versions of VB6/VBA'' (sic) (which, at this stage, there
won''t be) will destroy your asset(s). That''s like saying that no matter what
models of automobile may be developed in the future, the manufacturer will
always have to provide support for the particular model that I drive today.
In other words - ''I want to see innovation but I also want everything the
way it has always been''.

In objective 2 it states ''This core should be enhanced and extended, and
changes should follow a documented deprecation process.'' Am I the only one
who wonders how one can enhance and extend something and peprecate it at the
same time. To me ''enhance and extend'' and ''deprecate'' are complete
opposites.

In objective 3 it states ''The decisions of if, how and when to migrate code
to .NET should lie with the customer. Some may choose to remain with
unmanaged VB, especially for legacy code bases. Some will use only VB.NET,
others a mix.'' Please excuse my mistake in thinking that this is exactly the
case today and is not going to change on 1 April. Also, don''t forget about
the developers who are using a mix of VB6, VB.NET and C#.NET to provide
solutions.

In my personal experience I only encountered 2 ''issues'' in VB6 which needed
to be addressed by Microsoft and both were addressed in later service packs.
In the meantime a rather unattractive workaround was used to acheive the
desired result. While there was much gnashing of teeth at the time, the pain
soon passed. It does beg the question ''What new things are people attempting
to do with VB6 that are throwing up so many widespread issues that
mainstream support is still required?'' I am quickly coming to the view that
some are trying to use VB6 to do something that it is just not designed to
do and then criticising Microsoft when it doesn''t do it. If that is the case
then I''m afraid I cannot support that sort of behaviour. I also wonder if
some have been using mainstream support as an alternative to ''Read The
Flaming Manual'' or other methods of self-help support - It certainly appears
that many use these newgroups in that manner.

In some of the articles regarding this petition it talks about projects not
being migrated to VB.Net because it is complex. So what. An automobile is
complex compared to a bicycle but that doesn''t stop teenagers migrating from
the bike to the car. Complex does not mean difficult!!! Unfortunately there
are those who equate the two words and, in doing so, do nothing more than
make things difficult for themseleves. There are also those who seem
incapable of doing anything unless the entire wherewithall is handed to them
on a plate. Along with these are those who wring their hands and make
themselves sick with worry in case they don''t get a particular line of code
right the first time. To all those for whom the cap fits all I can say is,
get of your backsides, learn something for yourselves, be prepared to try
something. You''ll be surprised just how much one can get done when one is
not spending ones efforts in waiting for someone else to do it for one or
worrying if one has got it right first time.

To finish, I believe that Microsoft announced the timetable from ending
mainstream support for VB6 some 2 years ago, so I''m also wondering why it
has taken so long for a petition such as this to appear, or is it nothing
more than a knee-jerk reaction to the recent reminder.

Stephany

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:Ot*************@TK2MSFTNGP15.phx.gbl...

嗨Jim，
Jim Hubbard <再*** @ groups.please> schrieb：

Hi Jim,

"Jim Hubbard" <re***@groups.please> schrieb:

http： //www.eweek.com/article2/0,1759,1774642,00.asp

对于有兴趣签署请愿书的人：
<关于请愿的一般信息（新闻，博客文章等）：

http://classicvb.org/

签名清单：

http://classicvb.org/petition/

MS Herfried K. Wagner
MVP<网址：http：//dotnet.mvps.org/>
VB< URL：http：//classicvb.org/petition/>

For those who are interested in signing the petition:

General information (press, blog articles, etc.) about the petition:

http://classicvb.org/

List of signatures:

http://classicvb.org/petition/

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

UGH！


我从一开始就是VB开发人员。我于1991年9月从Galleria购物中心的Babbage'软件购买了我的第一份

VB版本1.

1991年以后从未回头过。

我和其他开发人员在

典型的争论中进行了许多宗教斗争，VB是一种真正的语言，可以用来真实地编写真实的

应用程序开发人员。


我已经非常了解它，花了无数个小时的学习，

学习并确保我像我一样理解语言可以。


所有这一切，甚至我认为它应该死得很死并被替换为

VB.NET


对VB Version 6的支持将于2005年3月31日结束。让它有尊严地死去和

尊重。


这是一个哀悼过去，朝着未来发展的时刻。


如果您想阅读其余内容，请访问以下链接访问我的博客...


http://spaces.msn.com/members/rcassick/Blog/cns ！1pXjHq-RqqMSQdLvn5n4gdnw！113.entry

" Herfried K. Wagner [MVP]" <喜*************** @ gmx.at>在消息中写道

新闻：Ot ************* @ TK2MSFTNGP15.phx.gbl ...

UGH!

I am a VB developer since the day it was born. I purchased my first copy of
VB version 1 from Babbage''s software at the Galleria mall in September of
1991 and have never looked back since.
I have gotten into many religious battles with other developers over the
typical arguments that VB is a real language that can be used to write real
applications by real developers.

I have gotten to know it very well, spending countless hours learning,
studying and making sure that I understood as much of the language as I can.

All that, and even I think it should die a quite death and be replaced by
VB.NET

Support for VB Version 6 ends on 3/31/2005. Let it die with dignity and
respect.

It is a time to mourn the past and grow towards the future.

If you want to read the rest visit my blog at the link below...

http://spaces.msn.com/members/rcassick/Blog/cns!1pXjHq-RqqMSQdLvn5n4gdnw!113.entry
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:Ot*************@TK2MSFTNGP15.phx.gbl...

嗨Jim，
Jim Hubbard <再*** @ groups.please> schrieb：

Hi Jim,

"Jim Hubbard" <re***@groups.please> schrieb:

http： //www.eweek.com/article2/0,1759,1774642,00.asp

对于有兴趣签署请愿书的人：
<关于请愿的一般信息（新闻，博客文章等）：

http://classicvb.org/

签名清单：

http://classicvb.org/petition/

MS Herfried K. Wagner
MVP<网址：http：//dotnet.mvps.org/>
VB< URL：http：//classicvb.org/petition/>

For those who are interested in signing the petition:

General information (press, blog articles, etc.) about the petition:

http://classicvb.org/

List of signatures:

http://classicvb.org/petition/

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

这篇关于微软MVP说他们想要老VB回来的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！