VB vs C#

[Gary K]

I first started with the C language using TurboC moving up to the full C++ with both borland/ms extensions. For the last couple of (dry) years, I have not needed to do full bore projects. As a result I switched to VB to make those quick util progs. Now that I am back into full(+1/2)-time coding, and using .NET now, I was wondering which direction would be better to take. I realise that I can create different 'modules' using either language and add them into a final project, but at the moment I am a one man team, so all the code will be mine. Which one is better for speed? and size? I've already noticed that VB.NET takes a lot of the drudgery out of code typing by auto-completing/formating a lot more than C# does, but C# provides a lot more control over events and interfaces. Does anyone have any thoughts or facts to put forward? I am interested in hearing what side other people have chosen and the reasons for it.

[Jon Skeet [C# MVP]]

Cor Ligthert <no**********@planet.nl> wrote:

I hope you understand the last row of this message, I see now, that I
corrected it to often.

The meaning is.
Maybe it is not exactly this code what is made (I see now too that it should
be minimal function with a return of the result)

However if it is this kind of code why should we than talk about the "with"/

If *what* is this kind of code?

I believe that With promotes less readable code, and therefore C# is
better without it. Just because you *can* write unreadable code in any
language doesn't mean that the language should encourage you to do so.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Cor Ligthert <no**********@planet.nl> wrote:

There is a very simple question in the VB.language group, almost everybody
was busy with it.
There is this sentence in.
dialogresult = me.show

My answer was this is not possible, when you want to do that it should be
with a new created form and a showdialog.
What was not possible? Sorry, you haven't said what the actual question
was...
I did not understand how he would do this. Now he says he got the program
from someone else and it is to complex for him to read. I think there is
something in that program as.
\\\
Shadows Sub Show()
Dim frm As New Form2
Dim result As DialogResult
result = frm.ShowDialog()
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, _
ByVal e As System.EventArgs) Handles Button1.Click
Me.Hide()
Me.Show()
Me.Button1.Parent.Show()
End Sub
///

I told that if this is true that he was working in my idea, as I call them,
by the maker obfuscated program.

Maybe it is not this code or something (I see now that it should be minimal
a function with a return of the result) however than you are talking about
the "with". Which what I said we agree. (second time in two days)

I'm afraid I really didn't follow any of that... what point were you
trying to make again?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[cody]

> > Using the keyword class for other purposes than declaring a class was my

idea too a few weeks ago.
I wanted to use it to get the current type of the class:

Yes, I remember. It was actually what finally gave me the bit of syntax I
needed for deciding on this.

static void Foo()
{
Type t = class
Console.Writeline("Iam declared in " + t);
}

I would rather see typeof(class) over just assigning class.

Yes thats what I meant, I just forgot the typeof().

Since GetType() is not available in static methods and hardcoding the
class
via typeof(MyClass) is errorprone and confusing,
I find using "class" here is completely fine.

--
cody

Freeware Tools, Games and Humour
http://www.deutronium.de.vu || http://www.deutronium.tk

[Jon Skeet [C# MVP]]

Cor Ligthert <no**********@planet.nl> wrote:

I hope you understand the last row of this message, I see now, that I
corrected it to often.

The meaning is.
Maybe it is not exactly this code what is made (I see now too that it should
be minimal function with a return of the result)

However if it is this kind of code why should we than talk about the "with"/

If *what* is this kind of code?

I believe that With promotes less readable code, and therefore C# is
better without it. Just because you *can* write unreadable code in any
language doesn't mean that the language should encourage you to do so.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[cody]

> > Using the keyword class for other purposes than declaring a class was my

idea too a few weeks ago.
I wanted to use it to get the current type of the class:

Yes, I remember. It was actually what finally gave me the bit of syntax I
needed for deciding on this.

static void Foo()
{
Type t = class
Console.Writeline("Iam declared in " + t);
}

I would rather see typeof(class) over just assigning class.

Yes thats what I meant, I just forgot the typeof().

Since GetType() is not available in static methods and hardcoding the
class
via typeof(MyClass) is errorprone and confusing,
I find using "class" here is completely fine.

--
cody

Freeware Tools, Games and Humour
http://www.deutronium.de.vu || http://www.deutronium.tk

[Cor Ligthert]

> What was not possible? Sorry, you haven't said what the actual question

was...

In a normal form
dialog result = me.show

Therefore I figured how it could been done. And I think it can be done with
this kind of code (I have shorten it for you)

Shadows function Show() as DialogResult
Dim frm As New Form2
return frm.ShowDialog()
End Sub

However this is weird in my opinion and add nothing, therefore I told what
are we talking about when people are even doing things like this.

Cor

[Cor Ligthert]

> What was not possible? Sorry, you haven't said what the actual question

was...

In a normal form
dialog result = me.show

Therefore I figured how it could been done. And I think it can be done with
this kind of code (I have shorten it for you)

Shadows function Show() as DialogResult
Dim frm As New Form2
return frm.ShowDialog()
End Sub

However this is weird in my opinion and add nothing, therefore I told what
are we talking about when people are even doing things like this.

Cor