c＃2004（惠德贝） [英] c# 2004 (Whidbey)

问题描述

刚读完2004年即将发布的功能

版本的VS.NET和C＃特别是
http://msdn.microsoft.com/vstudio/pr.../roadmap.aspx#

whidbey

看起来很好，我很高兴（关于泛型，分裂

类型...），除了1件事情

微软正在重新推出编辑并继续未来

for VB.NET ONLY ????

编辑并继续调试器中的功能不仅仅是简单的b $ b，而是关于拥有一个现代且功能强大的
调试器（测试器），它可以节省大量的时间来测试

代码（我记得在很久以前用vb我会写

只有方法的第一行，然后把它放到

调试模式并继续直到它是全部完成了，它是用b ++ .NET提供的
，它包含在ALL

现代Java IDE（JBuilder ..）中，现在它已经完成了回到VB.NET，

，这使得Visual C＃.NET成为唯一一款具有半调试器的现代和

流行语言？

请微软的某个人告诉我，我错了。

如果可以为VB和C ++做，那么我不会通过任何

解释，为什么它不能可以为c＃

谢谢

解决方案

当然，编辑并继续可以在C＃和VB中实现。 VB

用户要求它，因为他们习惯于在VB6中使用它，但根据MSFT，

C＃用户对此更加矛盾。少数人想要它，少数人认为这是一件坏事，大多数人都不在乎。就个人而言，我属于

不在乎。怀疑这可能是一件糟糕的事情，尽管我是b $ b试图保持开放的态度。我想我的想法是，在没有它20年的情况下，我已经得到了很好的b $ b，而且，我认为这对于工作代码很有用并且很有用在你的头脑中并通过桌面检查在你执行它之前，你需要执行它。良好的调试实践表明，在发布之前的某个时刻你会逐步浏览每一行

代码。


现在，我完全清楚我是''推广。一个工具并不一定是坏的

只是因为它能够被误用，或者因为它帮助那些没有能力的人在他们火上浇油之前得到更多的东西。而且很长一段时间，VB开发人员都错过了这个功能，也许还有一些功能。我只是

在我自己的工作中没有看到令人信服的需求，也没有一个

希望在我写它的时候逐行执行代码。


无论如何，从我读过的内容来看，MSFT公开表示，如果足够的话，那么C＃开发人员需要编辑并继续，他们我会实现它 - 但它实现起来并不是很简单，而且当C＃

开发人员看来，他们不想在上面花费资源为其他事情做好准备。


--BOB


" Arman Oganesian" < AO ******** @ msn.com>在留言中写道

news：05 **************************** @ phx.gbl ... < blockquote class =post_quotes>刚读完2004年即将发布的功能
版本的VS.NET和C＃特别是
http://msdn.microsoft.com/vstudio/pr.../roadmap.aspx#
whidbey
看起来很好，我很高兴（关于泛型，分裂
类型......），除了一件事情
微软正在重新引入编辑并继续。未来仅适用于VB.NET ????
编辑并继续调试器中的功能并不是关于简单性，而是关于拥有一个现代且功能强大的调试器（测试器），它可以节省大量的时间来测试代码（我记得很久以前用vb我只会写这个方法的第一行，然后把它放到
调试模式并继续直到它全部完成），它在C ++ .NET中可用，它是'包含在所有现代Java IDE（JBuilder ..）中，现在又回到VB.NET，这使得Visual C＃.NET成为唯一的现代和
流行语言有一半调试器吗？
请微软的某个人告诉我，我错了。
如果可以为VB和C ++做，那么我不会通过任何
解释，为什么它可以'不能为c＃
谢谢

" Bob Grommes" < bo*@bobgrommes.com>在消息中写道

新闻：％2 **************** @ TK2MSFTNGP12.phx.gbl ...

VB开发人员错过了这个功能，或许有一些东西。在我自己的工作中，我只是没有看到迫切的需求，也没有让我想要在我写的时候逐行执行代码。

我不认为调试和继续是什么意思。 D& C是打破错误，改变代码并让调试器再次从程序中的同一点启动

的能力，包括所有变量，在休息前与

相同的状态。


Colin

我绝对同意和你在一起开始编码之前应该在头部锻炼应用程序

，实际上是去年

和一半我一直在使用Rational XDE VS.NET

我已经习惯了它，所以即使我需要

创建4-5个类，我首先要用UML做，然后

生成存根，然后继续（实际上另一个

错过了VS.NET的功能，当你将XDE与

Visio进行比较时，然后Visio只是一个笑话，你不能用它做一个严肃的设计，因为Rational已成为IBM软件组的一部分。 ，破坏VS.NET的工作是＃b $ b，＃1，I想知道微软要做什么

，因为所有好的IDE都包含一些先进的案例

工具功能，即使是新的C＃Builder也会随之而来

基于Together Control Center，现在想象一下，如果IBM从VS.NET中删除了XDE，那么我将成为第一个转向

C的人#Builder）

但是回到编辑并继续，它不再是一个独特的VB功能，是的，它是在VB中开创的但是

现在C＃将是没有它的唯一主要工具，它是

a巨大的生产力提升，只是想象你有一个

Web应用程序已经实现了一些安全性，和你

不能简单地选择你工作的页面作为开始

页面，它会先发送你登录，任何时候你

需要对代码做一个小修复，你必须再次启动所有

，以及许多类似情况。

我认为这是一个蹩脚微软的借口说如果不是许多开发人员要求它b / b
那么我们就不会包括它了，很多C＃开发人员都不熟悉它或者你不是很好的b / b
不是很在乎它，因为之前没有使用它，

Java人们也没有要求它，但

它包括在所有专业中去年的Java IDE和

a一半，因为它是一个很好的生产力增强器和

节省了大量的时间，现在当C＃和Java正在进行时无论谁做出更好的工具，都可以吸引更多的人。

我知道这不是一件容易的事，用Java来做例如我

相信它背后的技术称为热插拔，

基本上可以替换一部分已编译的代码

苍蝇，

我会认为他们做了类似于VB.NET

（MSIL？）的事情所以大部分应该已经完成​​了，并相信
$ b $一旦你开始使用它并保存它时间，你会同意任何现代语言/ IDE /调试器不应该在没有它的情况下发布


Arman

-----原始消息-----
当然，编辑并继续可以用C＃实现
和VB一样。 VBuse在VB6中已经习惯了它，但是根据MSFT的说法，它是b $ b，C＃用户对此更加矛盾。少数人想要
，少数人认为这是一件坏事，大多数人都不在乎。个人
我属于不在乎。怀疑这可能是一件坏事b $ b，但我正在努力保持开放的态度。我想我的
的想法是，如果没有它，我已经好了20年了，而且，我认为
它是健康的，可以用来代码在脑海中工作并通过桌面 -
check"在你强行执行之前。良好的调试实践表明，在发布之前的某个时刻你通过代码的每一行都会花费
。

现在，我完全清楚我在推广。一个工具不一定是坏的，因为它能够被误用，或者因为它b $ b可以让它们在火焰下降之前更远。和
一样，很多时候开发人员都错过了这个功能，也许它的价格是b $ b。在我自己的工作中，我还没有看到对它的迫切需求，也没有我在写这篇文章的时候曾经有过逐行执行代码的想法。

无论如何，底线，根据我的阅读，如果足够的C＃开发人员要求编辑并继续，MSFT会公开表示
，他们将实施
它 - 但它实施起来并不重要，而且当C＃开发人员似乎忙于其他事情时，我们不想花费
资源。

--BOB

Arman Oganesian < AO ******** @ msn.com>在消息中写道
新闻：05 **************************** @ phx.gbl ...

刚读完2004年即将发布的功能
版本的VS.NET和C＃特别是
http://msdn.microsoft.com/vstudio/pr.../roadmap.aspx# whidbey
看起来不错，我很开心（关于泛型，拆分类型......），除了1件事之外微软正在重新引入编辑并继续。
VB.NET的未来只有????
编辑并继续调试器中的功能不是关于简单性，而是关于拥有一个现代且功能强大的调试器（测试器），它可以节省大量时间来测试代码
（我记得很久以前用vb我只会写这个方法的第一行，然后把它放到
调试模式并继续直到它全部完成），
它在C ++ .NET中可用，它是'包含在所有现代Java IDE（JBuilder ..）中，现在又回到
VB.NET，这使得Visual C＃.NET成为唯一的现代和
流行语言有一半调试器吗？
请微软的某个人告诉我，我错了。
如果可以为VB和C ++做，那么我不会通过任何
解释，为什么它可以'不能为c＃
谢谢

。

Just finished reading about upcoming features in 2004
version of VS.NET and C# in particular
http://msdn.microsoft.com/vstudio/pr.../roadmap.aspx#
whidbey
Looks good and I am very happy (about generics, split
types...), Except 1 thing
Microsoft is reintroducing the "Edit and continue" future
for VB.NET ONLY????
The "Edit and Continue" functionality in debugger is NOT
about simplicity, but about having a modern and powerful
debugger(tester) which saves a LOT of time in testing the
code(I remember in good old times with vb I would write
only the first line of the method, then put it into
debugging mode and continue until it was all finished), it
was available in C++.NET, it''s included in ALL
modern Java IDEs(JBuilder..), and now it''s back to VB.NET,
by that making the Visual C#.NET the only modern and
popular language with half debugger??
Please someone from Microsoft tell me that I am wrong.
If it can be done for VB and C++, then I will not by any
explanation, why it can''t be done for c#
Thank you

解决方案

Sure, "Edit and Continue" can be implemented in C# as well as in VB. VB
users demand it as they were accustomed to it in VB6, but according to MSFT,
C# users are more ambivalent about it. A minority want it, a minority think
it''s a Bad Thing, and most don''t really care. Personally I fall into the
"don''t care" camp with suspicions that it could be a Bad Thing, although I''m
trying to remain open-minded about it. I guess my thinking is, I''ve gotten
along fine without it for 20 years, and besides, I think it''s healthy and
useful to work code out in your head and via "desk-checking" before you ever
execute it. Good debugging practice says you step through every line of
code anyway at some point before release.

Now, I''m fully aware that I''m generalizing. A tool isn''t necessarily bad
just because it''s capable of being misused or because it helps the witless
get farther along before they go down in flames. And as much as long-time
VB developers miss the feature, perhaps there''s something to it. I just
haven''t seen a compelling need for it in my own work, nor have I ever had a
desire to execute code line by line as I write it.

Anyway, bottom line, from what I''ve read, MSFT is saying publicly if enough
C# developers demand edit-and-continue, they''ll implement it -- but it''s not
trivial to implement, and they don''t want to expend resources on it when C#
developers seem to be clamboring for other things.

--Bob

"Arman Oganesian" <ao********@msn.com> wrote in message
news:05****************************@phx.gbl...

Just finished reading about upcoming features in 2004
version of VS.NET and C# in particular
http://msdn.microsoft.com/vstudio/pr.../roadmap.aspx#
whidbey
Looks good and I am very happy (about generics, split
types...), Except 1 thing
Microsoft is reintroducing the "Edit and continue" future
for VB.NET ONLY????
The "Edit and Continue" functionality in debugger is NOT
about simplicity, but about having a modern and powerful
debugger(tester) which saves a LOT of time in testing the
code(I remember in good old times with vb I would write
only the first line of the method, then put it into
debugging mode and continue until it was all finished), it
was available in C++.NET, it''s included in ALL
modern Java IDEs(JBuilder..), and now it''s back to VB.NET,
by that making the Visual C#.NET the only modern and
popular language with half debugger??
Please someone from Microsoft tell me that I am wrong.
If it can be done for VB and C++, then I will not by any
explanation, why it can''t be done for c#
Thank you

"Bob Grommes" <bo*@bobgrommes.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

VB developers miss the feature, perhaps there''s something to it. I just
haven''t seen a compelling need for it in my own work, nor have I ever had a desire to execute code line by line as I write it.

I don''t think that''s what is meant by "debug and continue." D&C is the
ability to break on an error, change the code and have the debugger start up
again from the same point in the program, with all variables, etc. in the
same state as before the break.

Colin

I absolutely agree with you that one should workout the app
in the head before start coding, in fact for a last year
and a half I''ve been using the Rational XDE with VS.NET
and I''ve got used to it so match that even if I need to
create 4-5 classes, first I will do it with UML, then
generate the stub, and then continue(In fact another
missed capability from VS.NET, when you compare XDE with
Visio, then Visio is just a joke, you can''t do a serious
design with it, and since the Rational has become part of
the IBM''s software group, for which destroying VS.NET is
the job # 1, I wonder what is Microsoft is going to do
about it, since all good IDEs include some advanced case
tool capabilities, even new C#Builder will come with it
based on Together Control Center, and now imagine if IBM
drops XDE from VS.NET?, I will be the first one to move to
C#Builder)
But back to "Edit and continue", it is not anymore an
exclusive VB feature, yes it was pioneered in the VB but
now C# will be the only major tool without it, and it is
a huge productivity enhancement, just imagine you have a
Web app with some security already implemented, and you
can''t just simply select the page you work on as a start
up page, it will send you to login first, and any time you
need to make a small fix to code you have to start all
over again, and many similar situations.
I think it is a lame excuse for Microsoft say that if not
to many developers demanding it then we will not include
it, many C# developers are not familiar with it or as you
don''t really care about it because did not use it before,
the Java people didn''t ask for it too, but
It is included in all major Java IDEs for a last year and
a half, because it''s a great productivity enhancer and
saves a lot of time, and now when C# and Java are going
neck to neck, whoever makes better tools may attract more
people.
I know it''s not easy thing to do, in Java for example I
believe the technology behind it called "Hot Swap",
basically being able to replace piece of compiled code on
the fly,
I would think that they did something similar forVB.NET
(MSIL?)so most of it should be already done, and believe
me once you start using it and saving the time, you will
agree that any modern Language/IDE/Debugger should not be
released without it
Arman

-----Original Message-----
Sure, "Edit and Continue" can be implemented in C# as well as in VB. VBusers demand it as they were accustomed to it in VB6, but according to MSFT,C# users are more ambivalent about it. A minority want it, a minority thinkit''s a Bad Thing, and most don''t really care. Personally I fall into the"don''t care" camp with suspicions that it could be a Bad Thing, although I''mtrying to remain open-minded about it. I guess my thinking is, I''ve gottenalong fine without it for 20 years, and besides, I think it''s healthy anduseful to work code out in your head and via "desk- checking" before you everexecute it. Good debugging practice says you step through every line ofcode anyway at some point before release.

Now, I''m fully aware that I''m generalizing. A tool isn''t necessarily badjust because it''s capable of being misused or because it helps the witlessget farther along before they go down in flames. And as much as long-timeVB developers miss the feature, perhaps there''s something to it. I justhaven''t seen a compelling need for it in my own work, nor have I ever had adesire to execute code line by line as I write it.

Anyway, bottom line, from what I''ve read, MSFT is saying publicly if enoughC# developers demand edit-and-continue, they''ll implement it -- but it''s nottrivial to implement, and they don''t want to expend resources on it when C#developers seem to be clamboring for other things.

--Bob

"Arman Oganesian" <ao********@msn.com> wrote in message
news:05****************************@phx.gbl...

Just finished reading about upcoming features in 2004
version of VS.NET and C# in particular
http://msdn.microsoft.com/vstudio/pr.../roadmap.aspx# whidbey
Looks good and I am very happy (about generics, split
types...), Except 1 thing
Microsoft is reintroducing the "Edit and continue" future for VB.NET ONLY????
The "Edit and Continue" functionality in debugger is NOT
about simplicity, but about having a modern and powerful
debugger(tester) which saves a LOT of time in testing the code(I remember in good old times with vb I would write
only the first line of the method, then put it into
debugging mode and continue until it was all finished), it was available in C++.NET, it''s included in ALL
modern Java IDEs(JBuilder..), and now it''s back to VB.NET, by that making the Visual C#.NET the only modern and
popular language with half debugger??
Please someone from Microsoft tell me that I am wrong.
If it can be done for VB and C++, then I will not by any
explanation, why it can''t be done for c#
Thank you

.

这篇关于c＃2004（惠德贝）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！