C＃或VB ..有没有人决定哪一个对团队有利。 [英] C# or VB.. Did anybody go about deciding which one is good for the team.

问题描述

我知道两者几乎相同而且归结为个人选择。

但是我必须为团队做出选择。到目前为止的事情，我是

考虑到

1. C＃中的XML文档 - 那很好..在VB.net中不存在？？

2.像Redim这样的VB.Net的一些语言功能（使得b $ b $开发人员更容易），但还不够好。


3. C＃更像标准语言，使用的关键词更符合b $ b标准。它使C＃开发人员更容易与其他类似于C语言的
开发人员进行交流。


4.转向C＃可能会有更高的学习具有VB

背景的开发人员的曲线。但我认为C＃可以帮助鼓励良好的开发

实践，语言本身比VB.Net更简单


5.最后我想如果你正在开发多层应用程序，我是

靠开发C＃中间层和演示文稿

VB.Net ..它只是RAD。


关于此的想法和其他意见请!!! :)


KN

I know both are pretty much the same and it comes down to personal choice.
But I have to make the choice for the team. Things so far that I am
considering

1. XML documentation in C# -- thats good.. not there in VB.net??

2. Some language features of VB.Net like Redim(makes it easier for
developers), but not good enough reason.

3. C# is in more like standard languages and key words used are more
standard. It kind of makes it easier for C# developers to communicate with
developers in other languages similar to C.

4. Moving to C# might have a higher learning curve for a developer with a VB
background. But I think C# can help in encouraging good development
practices and the language itself is simpler than VB.Net

5. Finally I think if you are developing multi layered application, I am
leaning on developing the middle tier in C# and the presentation with
VB.Net.. Its just RAD.

Thoughts and other opinions on this please!!! :)

KN

推荐答案

首先，你不应该需要Redim。我还没有，动态增长的收藏品

非常擅长。你几乎不需要阵列

。


我认为＃3不是一个足够好的理由，考虑到已经有了
$事实上，你有VB开发人员。


正如你自己所说，语言非常相似。每个都有功能

，另一个没有。但如果这不是问题，

那么语言选择也不是。


既然你有VB团队，他们应该继续使用VB，因为这将是

最小的学习曲线。一旦他们知道并熟悉.NET，他们就会很容易地学习C＃，因为大多数东西都是一对一的b
。


另外，如果你在谷歌群组上进行搜索，你将会有大约1000个线程与

相同的问题...


" ; KN" < [e-mail]>在消息中写道

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

First off, you should not need Redim. I haven''t yet, the collection objects
that grow dynamically are very good at this. And you hardly ever need arrays
at all.

I think #3 is not a good enough reason, considering there is already the
fact that you have VB developers.

As you said yourself, the language are very similar. There is functionality
in each of them, that the other does not have. But if this is not an issue,
then the language choice is not either.

Since you have a VB team, they should continue to use VB, as this will have
the smallest learning curve. Once they know and are comfortable with .NET,
they will easily learn C#, as for most thing there is a one to one
correspondance.

Also, if you do a search on google groups, you will about 1000 threads with
the same question...

"KN" <[e-mail]> wrote in message
news:Ot**************@TK2MSFTNGP11.phx.gbl...

我知道两者都很漂亮大致相同，这取决于个人选择。
但我必须为团队做出选择。到目前为止，我正在考虑的事情

1. C＃中的XML文档 - 那很好..在VB.net中不存在吗？

2.一些像Redim这样的VB.Net的语言功能（使开发人员更容易），但还不够好。

3. C＃更像标准语言，使用的关键词更多<标准。它使C＃开发人员更容易与其他类似于C语言的开发人员进行交流。

4.转移到C＃可能会为具有$ b的开发人员提供更高的学习曲线$ b VB背景。但我认为C＃可以帮助鼓励良好的开发实践，语言本身比VB.Net更简单。

5.最后我想如果你正在开发多层应用程序，我是
关于这个的想法和其他意见请!!! :)

KN

I know both are pretty much the same and it comes down to personal choice.
But I have to make the choice for the team. Things so far that I am
considering

1. XML documentation in C# -- thats good.. not there in VB.net??

2. Some language features of VB.Net like Redim(makes it easier for
developers), but not good enough reason.

3. C# is in more like standard languages and key words used are more
standard. It kind of makes it easier for C# developers to communicate with
developers in other languages similar to C.

4. Moving to C# might have a higher learning curve for a developer with a VB background. But I think C# can help in encouraging good development
practices and the language itself is simpler than VB.Net

5. Finally I think if you are developing multi layered application, I am
leaning on developing the middle tier in C# and the presentation with
VB.Net.. Its just RAD.

Thoughts and other opinions on this please!!! :)

KN

查看以下链接：

http://support.microsoft.com/?kbid=308470

http://www.desaware.com/Ebook2L2.htm


内联其他评论...

Check out these links:

http://support.microsoft.com/?kbid=308470

http://www.desaware.com/Ebook2L2.htm

Other comments inline...

1. C＃中的XML文档 - 这很好..不存在VB.net？


它没有内置到VB.Net中，但是有几个插件可以添加这个

功能。

< a rel =nofollowhref =http://www.gotdotnet.com/team/ide/target =_ blank> http://www.gotdotnet.com/team/ide/

http://msdn.microsoft.com/library/de...MLComments.asp

IDE只有一个功能对于VB.Net - 后台编译。

它立即警告你在任务列表中使用squggly line和

错误消息编码错误，而不是让你等待直到编译。

我喜欢它，并且在用C＃编码时会错过它。其他人觉得很烦人。

2.像Redim这样的VB.Net的一些语言功能（使开发人员更容易），但还不够好。
3. C＃更像标准语言，使用的关键词更符合标准。它使C＃开发人员更容易与其他类似于C语言的开发人员进行交流。


如你所说，选择C＃或VB.Net真的只是一个个人

偏好 - 他们两个可以做几乎完全相同的事情与

相同的表现。 （是的，C＃会让你使用不安全的代码，但是你想要或者需要多少时间？）VB有更多的keywoards - 有些是有用的

（比如With / EndWith）构造，以及一些你可能想要避免的主要是传统的

关键字。 （我尝试尽可能使用.Net Framework

方法，而不是VB关键字。）


如果您和您的开发团队更熟悉C风格的关键字

和语言结构，与C＃一起使用。如果您更熟悉Visual

Basic，请使用VB.Net。


4.转到C＃可能会有更高的学习曲线具有
VB背景的开发人员。但我认为C＃可以帮助鼓励良好的开发实践，语言本身比VB更简单。


有效的考虑因素。一个VB6开发人员只是在没有

适当培训的情况下移动到VB.Net可能会产生一些坏习惯。最大的范式转换

是VB.Net现在是一种完全面向对象的语言，需要花费一些时间才能习惯这个。更重要的考虑因素是确保开发人员获得足够的关于新语言的教育 -

无论是C＃还是VB.Net。 （对于VB6来说，有几本优秀的书正在转向VB.Net，特别是来自APress的程序员。）


5.最后我想如果你是开发多层应用程序，我倾向于用C＃开发中间层和用VB.Net进行演示..它只是RAD。

1. XML documentation in C# -- thats good.. not there in VB.net??
It''s not built into VB.Net, but there are several plugins that add this
functionality.

http://www.gotdotnet.com/team/ide/

http://msdn.microsoft.com/library/de...MLComments.asp

The IDE has one feature that''s only for VB.Net -- background compilation.
It immediately warns you about coding errors with a squggly line and an
error message in the task list, rather than making you wait until compiling.
I love it, and miss it when coding in C#. Other people find it annoying.
2. Some language features of VB.Net like Redim(makes it easier for
developers), but not good enough reason.

3. C# is in more like standard languages and key words used are more
standard. It kind of makes it easier for C# developers to communicate with
developers in other languages similar to C.
As you mentioned, selecting C# or VB.Net really is just a personal
preference -- they both can do almost exactly the same things with about the
same performance. (Yes, C# will let you use unsafe code, but how often will
you want or need to do that?) VB has more keywoards -- some that are useful
(like the With/EndWith) constructs, and some that are primarily legacy
keywords that you might want to avoid. (I try to use the .Net Framework
methods, rather than VB keywords, wherever possible.)

If you and your development team are more comfortable with C-style keywords
and language constructs, go with C#. If you''re more familiar with Visual
Basic, go with VB.Net.

4. Moving to C# might have a higher learning curve for a developer with a VB background. But I think C# can help in encouraging good development
practices and the language itself is simpler than VB.Net
A valid consideration. A VB6 developer who just moves to VB.Net without the
proper training could develop some bad habits. The biggest paradigm shift
is that VB.Net is now a fully object-oriented language, and it takes some
time to get used to this. The more important consideration is to ensure
that the developers get enough education regarding the new language --
whether it''s C# or VB.Net. (There are several good books for VB6
programmers who are moving to VB.Net, particularly from APress.)

5. Finally I think if you are developing multi layered application, I am
leaning on developing the middle tier in C# and the presentation with
VB.Net.. Its just RAD.

不要混淆和混淆语言只是出于那就是'它是如何完成'b
。您可以轻松地将VB.Net用于两个层，C＃用于

层，或者C＃用于表示层，VB.Net用于中间层。我认为你的理由只是过去的一段时间，因为它有更好的RAD功能用于开发用户，因为VB6用于前端是因为它有更好的RAD功能用于开发用户

接口，C ++用于中间层，因为它具有更好的性能和功能。这些注意事项不再适用。


使用这两种语言并没有什么问题，并且学习两种语言都有好处。但是如果你的程序员对一种语言的b / b语言更有经验，那么坚持使用那种语言来进行日常开发是更好的做法。


希望这会有所帮助，


Robert Jacobson

Don''t mix-and-match the languages just out of a sense that "that''s how it''s
done." You could just as easily use VB.Net for both layers, C# for both
layers, or C# for the presentation layer and VB.Net for the middle tier. I
think that your rationale is just a holdover from the old days when VB6 was
used for front-ends because it had better RAD features for developing user
interfaces, and C++ was used for the middle layer because of better
performance and power. These considerations no longer apply.

There''s nothing wrong with using both languages, and there''s a benefit to
learning both. But if your programmers are more experienced with one
language, it would be a better practice just to stick to that language for
day-to-day development.

Hope this helps,

Robert Jacobson

您好

同意大多数要点，但对于第一个要点：

Hi
Agree with most of the points but for the first one :

首先，你不应该需要Redim。我还没有，动态增长的
集合对象非常擅长。而你
几乎不需要数组。


凭借系列提供的功能，可能会有完全取消数组的倾向。这可能是因为该系列提供的爵士方法和

相关课程可能很有吸引力。但是这里有一个

性能问题


请注意，集合采用对象的参数

类型。这意味着如果我使用一个集合存储一个

组的整数值，每次我添加/检索一个

整数时，都会有一个装箱和拆箱（这个是昂贵的b $ b。数组在这里更适合你可以声明

整数数组，添加/检索相同的没有任何

问题。


所以我觉得收藏品很好

a）你使用参考类型

b）你想在一个对象中分组多种类型的数据

c ）你不知道对象的类型，它将被动态地知道

，但是你想要一个可以容纳所有类型的通用对象




所以如果

a）你在设计时明确知道类型

b）该组中的所有类型都是同质的

然后阵列更好


如果有人对此有任何意见，我将不胜感激


问候，
< br $>
sr


问候，


sr

-----原帖-----
首先，你不应该需要Redim。我还没有，动态增长的
集合对象非常擅长。而你只需要b $ b就几乎不需要数组。

我认为＃3不是一个足够好的理由，考虑到你有VB开发人员已经确定了
。

正如你自己所说，语言非常相似。
每个都有功能，另一个没有功能。但是如果
这不是问题，那么语言选择也不是。

由于你有VB团队，他们应该继续使用VB，
因为这将有最小的学习曲线。一旦他们知道并且对.NET感到满意，他们就会轻松学习C＃，因为对于大多数事情来说，一对一对应的价格是
。

此外，如果你进行搜索在google群组中，你会有大约
1000个主题同样的问题...

  KN" < [e-mail]>在消息中写道
新闻：Ot ************** @ TK2MSFTNGP11.phx.gbl ...

First off, you should not need Redim. I haven''t yet, the collection objectsthat grow dynamically are very good at this. And you hardly ever need arraysat all.
With the features offered by collections, there might be
a tendency to do away with arrays completely. This could
be coz the jazzy methods offered by the collection and
related classes might be attractive. But there is a
performance issue here

Do note that collection takes a parameter of the object
type. this means that if i use a collection to store a
group of integer values , every time i add/retrieve an
integer, there will be a boxing and unboxing(which is
costly). Arrays are more suitable here coz u can declare
an integer array, add/retrieve the same without any
problems.

So i feel that collections are good when
a) u use reference types
b)u want to group multiple types of data in a single object
c)u do not know the type of the object and it wil be known
dynamically, but u want a generic object which can hold
all the types

So If
a) you know the type clearly at design time
b) all the types in the group are homogenous

then arrays are better

Would appreciate if some one has any comments on this

regards,

sr

regards,

sr
-----Original Message-----
First off, you should not need Redim. I haven''t yet, the collection objectsthat grow dynamically are very good at this. And you hardly ever need arraysat all.

I think #3 is not a good enough reason, considering there is already thefact that you have VB developers.

As you said yourself, the language are very similar. There is functionalityin each of them, that the other does not have. But if this is not an issue,then the language choice is not either.

Since you have a VB team, they should continue to use VB, as this will havethe smallest learning curve. Once they know and are comfortable with .NET,they will easily learn C#, as for most thing there is a one to onecorrespondance.

Also, if you do a search on google groups, you will about 1000 threads withthe same question...

"KN" <[e-mail]> wrote in message
news:Ot**************@TK2MSFTNGP11.phx.gbl...

我知道两者几乎是一样的对于个人选择，它降低了
。但我必须为团队做出选择。事情如此美元b $ b远远我正在考虑的问题

1. C＃中的XML文档 - 那很好..没有
VB.net ??
2.有些像Redim这样的VB.Net的语言功能（让开发人员更容易获得
），但还不够好。

3. C＃更像是标准语言和关键词
使用更标准。它使C＃开发人员更容易与其他类似C语言的开发人员进行交流。

4.转向C＃可能会为
a开发人员带来更高的学习曲线a

I know both are pretty much the same and it comes down to personal choice. But I have to make the choice for the team. Things so far that I am considering

1. XML documentation in C# -- thats good.. not there in VB.net??
2. Some language features of VB.Net like Redim(makes it easier for developers), but not good enough reason.

3. C# is in more like standard languages and key words used are more standard. It kind of makes it easier for C# developers to communicate with developers in other languages similar to C.

4. Moving to C# might have a higher learning curve for a developer with a

VB

background。但我认为C＃可以帮助鼓励好的

background. But I think C# can help in encouraging good

开发实践，语言本身比VB.Net简单。

5.最后我想如果您正在开发多层
应用程序，我倾向于使用VB.Net开发C＃中的中间层和
演示文稿..它只是RAD。

思想和其他请对此提出意见!!! :)

KN

development practices and the language itself is simpler than VB.Net

5. Finally I think if you are developing multi layered application, I am leaning on developing the middle tier in C# and the presentation with VB.Net.. Its just RAD.

Thoughts and other opinions on this please!!! :)

KN

。

.

这篇关于C＃或VB ..有没有人决定哪一个对团队有利。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！