VB.NET程序员的C＃ [英] C# for VB.NET Programmers
问题描述
对于希望迁移到C＃的VB.NET程序员是否有一个很好的教程？
我找到了几个教程，假设这个人是新的
一般的编程，我发现有一些人认为这个人是从B ++迁移的，但是我还没有找到任何符合
经验的人VB.NET开发人员。
我找到了一个快速参考，比较了
二的语言结构（ http://www.harding.edu/USER/fmccown/...omparison.html ）
但理想情况下我也想找一些教程。
另外，为什么C＃开发人员坚决反对WITH语句？我刚刚写了我的第一个C＃网络应用程序，我有大约20行代码，所有这些代码都是uwgOrphans.HeaderStyleDefault.Style的属性。我结束了
只需手动键入所有内容，但在这种情况下，WITH-like语句将保存大约700个字符的
。我已经读过替代品了，但是他们要么不建议使用
（在使用的情况下）或者他们不携带Intellisense
（in将其传递给另一种方法的情况）。我不打算抱怨或开始一场火焰战，我只是好奇为什么C＃开发者整体上说
不喜欢甚至让它作为一种选择出现的想法。
问候，
Scott McNair
我主要是在VB开发人员，但我也不喜欢''with''声明。我已经发现更难以读取缺少变量名的代码。如果我
大量使用变量，我会复制它并粘贴它，所以我不必一直输入
。但对我来说，每次都有整个变量，
使它更具可读性。另外，我不喜欢额外的缩进级别
附带一个''with''声明。
" Scott McNair" < sc ********** @ sfmco.takethispartout.com写在留言中
新闻：Xn ****************** ** @ 207.46.248.16 ...
是否有一个很好的VB.NET程序员教程，希望迁移到C＃？
我'已经找到了几个教程，假设这个人一般都是新编的b / b
编程，而且我发现一些假设这个人
是
从C ++迁移，但我还没有找到任何迎合
经验丰富的VB.NET开发人员。
我''我找到了一个快速参考，比较
二的语言结构（ http://www.harding.edu/USER/fmccown/...omparison.html ）
但理想情况下我想找到一些教程也是如此。
另外，为什么C＃开发人员坚决反对WITH语句？我刚刚写了我的第一个C＃网络应用程序，我有大约20行代码，所有这些代码都是uwgOrphans.HeaderStyleDefault.Style的属性。我结束了
只需手动键入所有内容，但在这种情况下，WITH-like语句将保存大约700个字符的
。我已经读过替代品了，但是他们要么不建议使用
（在使用的情况下）或者他们没有携带
Intellisense
（在将其传递给另一个方法的情况下）。我不打算抱怨
或
开始一场火焰战，我只是好奇为什么C＃开发者作为一个整体
不喜欢将它作为一个选项出现的想法。
问候，
Scott McNair
" Scott McNair" < sc ********** @ sfmco.takethispartout.com写在留言中
新闻：Xn ****************** ** @ 207.46.248.16 ...
是否有一个很好的VB.NET程序员教程，希望迁移到C＃？
我'已经找到了几个教程，假设这个人一般都是新编的b / b
编程，而且我发现一些假设这个人
是
从C ++迁移，但我还没有找到任何迎合经验丰富的VB.NET开发人员的b
。
有一本名为The .NET Languages：A Quick Translation Guide的书。通过
Brian Bischof。将VB.NET内容翻译成
C＃非常有用。
http://www.amazon.com/ gp / product / 189 ... e = UTF8& s =书籍
- Alan
Scott ，
实际上我相信从VB.NET转到C＃的最好的教程之一是使用Reflector并将你的VB.NET Stuff反编译成C＃的
。不仅很棒
练习，但它会立即让你完全了解
vb.net的变幻莫测（特别是如果Option Strict和Option Explicit没有设置为On！
Peter
-
联合创始人，Eggheadcafe.com开发者门户网站：
http://www.eggheadcafe.com
UnBlog：
http://petesbloggerama.blogspot.com
" Scott McNair"写道：
是否有一个很好的VB.NET程序员教程，希望迁移到C＃？
我找到了几个教程，假设这个人一般都是新的编程，而且我发现一些人认为这个人是
从C ++迁移，但我还没有找到任何满足经验丰富的VB的b / b
。 NET开发人员。
我找到了一个快速参考，比较了
二的语言结构（ http://www.harding.edu/USER/fmccown/...omparison.html ）
但理想情况下我也想找一些教程。
另外，为什么C＃开发人员坚决反对WITH语句？我刚刚写了我的第一个C＃网络应用程序，我有大约20行代码，所有这些代码都是uwgOrphans.HeaderStyleDefault.Style的属性。我结束了
只需手动键入所有内容，但在这种情况下，WITH-like语句将保存大约700个字符的
。我已经读过替代品了，但是他们要么不建议使用
（在使用的情况下）或者他们不携带Intellisense
（in将其传递给另一种方法的情况）。我不打算抱怨或开始一场火焰战，我只是好奇为什么C＃开发者整体上说
不喜欢甚至让它作为一种选择出现的想法。
问候，
Scott McNair
Is there a good tutorial for VB.NET programmers looking to migrate to C#?
I''ve found several tutorials that assume that the person is new to
programming in general, and I''ve found a few that assume that the person is
migrating from C++, but I have yet to find any that cater to the
experienced VB.NET developer.
I''ve found a quick reference that compare the language structures of the
two (http://www.harding.edu/USER/fmccown/...omparison.html)
but ideally I''d like to find some tutorials as well.
Also, why are C# developers so adamantly opposed to the WITH statement? I
just wrote my first C# web app, and I had about 20 lines of code that all
referred to properties of uwgOrphans.HeaderStyleDefault.Style. I wound up
just hand-keying it all, but in this case a WITH-like statement would have
saved about 700 characters. I''ve read of alternatives, but they''re either
not recommended (in the case of USING) or they don''t carry the Intellisense
(in the case of passing it to another method). I''m not looking to gripe or
to start a flame war, I''m just curious as to why C# developers as a whole
don''t like the idea of even having it present as an option.
Regards,
Scott McNair
I developer mostly in VB, but I don''t like the ''with'' statement either. I''ve
also found it harder to read the code with the variable name missing. If I
use a variable a lot, I copy it, and paste it so I don''t have to type it out
all the time. But for me, having the entire variable there, every time,
makes it far more readable. Plus, I don''t like the extra level of indenting
that comes with having a ''with'' statement.
"Scott McNair" <sc**********@sfmco.takethispartout.comwrote in message
news:Xn********************@207.46.248.16...Is there a good tutorial for VB.NET programmers looking to migrate to C#?
I''ve found several tutorials that assume that the person is new to
programming in general, and I''ve found a few that assume that the person
is
migrating from C++, but I have yet to find any that cater to the
experienced VB.NET developer.
I''ve found a quick reference that compare the language structures of the
two (http://www.harding.edu/USER/fmccown/...omparison.html)
but ideally I''d like to find some tutorials as well.
Also, why are C# developers so adamantly opposed to the WITH statement? I
just wrote my first C# web app, and I had about 20 lines of code that all
referred to properties of uwgOrphans.HeaderStyleDefault.Style. I wound up
just hand-keying it all, but in this case a WITH-like statement would have
saved about 700 characters. I''ve read of alternatives, but they''re either
not recommended (in the case of USING) or they don''t carry the
Intellisense
(in the case of passing it to another method). I''m not looking to gripe
or
to start a flame war, I''m just curious as to why C# developers as a whole
don''t like the idea of even having it present as an option.
Regards,
Scott McNair
"Scott McNair" <sc**********@sfmco.takethispartout.comwrote in message
news:Xn********************@207.46.248.16...Is there a good tutorial for VB.NET programmers looking to migrate to C#?
I''ve found several tutorials that assume that the person is new to
programming in general, and I''ve found a few that assume that the person
is
migrating from C++, but I have yet to find any that cater to the
experienced VB.NET developer.There is a book called "The .NET Languages: A Quick Translation Guide" by
Brian Bischof. It is very helpful for translating the VB.NET stuff into
C#.
http://www.amazon.com/gp/product/189...e=UTF8&s=books
-- Alan
Scott,
Actually I believe one of the best tutorials on moving from VB.NET to C# is
to use Reflector and decompile your VB.NET Stuff into C#. Not only great
practice, but it will instantly make you fully aware of the vagaries of
vb.net (especially if Option Strict and Option Explicit weren''t set to "On"!
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"Scott McNair" wrote:
Is there a good tutorial for VB.NET programmers looking to migrate to C#?
I''ve found several tutorials that assume that the person is new to
programming in general, and I''ve found a few that assume that the person is
migrating from C++, but I have yet to find any that cater to the
experienced VB.NET developer.
I''ve found a quick reference that compare the language structures of the
two (http://www.harding.edu/USER/fmccown/...omparison.html)
but ideally I''d like to find some tutorials as well.
Also, why are C# developers so adamantly opposed to the WITH statement? I
just wrote my first C# web app, and I had about 20 lines of code that all
referred to properties of uwgOrphans.HeaderStyleDefault.Style. I wound up
just hand-keying it all, but in this case a WITH-like statement would have
saved about 700 characters. I''ve read of alternatives, but they''re either
not recommended (in the case of USING) or they don''t carry the Intellisense
(in the case of passing it to another method). I''m not looking to gripe or
to start a flame war, I''m just curious as to why C# developers as a whole
don''t like the idea of even having it present as an option.
Regards,
Scott McNair
这篇关于VB.NET程序员的C＃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
