hey, I don't want to alarm anyone but I think you got some dead pixels there or perhaps a Baby.Paint.Virus.Writer there... look at those black lines O.o xD
there would be the product key. however it was funny at all xD
******. C++ is used by many people (most implementations lack a lot though, imo), but for beginners, I would NEVER EVER recommend it.
Advanced pointers for beginning programmers? Don't make me laugh.
@OP: You probably won't notice the differences between VS and VS Express.
I would choose C# though, because VB is older and just umm... annoying and ugly.
You'll get much further with C#, because it's newer and optimized for use with the .Net framework and it will be easier to change to C/C++ if you would ever want to.
I have to agree with lesderid. C# is the perfect language to start with. It's quite easy to learn and the syntax is more common so it's easier to learn other languages.
I started with C(in school) and i have to say that it was pretty easy to learn.
After C we made Java and it was **** easy to learn. I never really made Programs in any other Language, but if i look at the source of a program written in C++,C# i easily understand whats written there
So starting with C or even with C++ wouldn't be that wrong
Vb.net and c# are both .net languages so they look just similiar. I advise you starting from vb.net , in time you will already see alot of c# projects and will comfortably code both. But still , you should prefer vb.net because some of things are easier and shortcuts etc in language , but as i said it doesnt matter at all choose what you want to.
Ps . I started in vb.net and im still coding there , well even tho im not a pro i can comfortably read and write c# but i still love vb.net ( don't know , preferring writing Hex instead of conversions.touint16 , lol )
Vb.net and c# are both .net languages so they look just similiar. I advise you starting from vb.net , in time you will already see alot of c# projects and will comfortably code both. But still , you should prefer vb.net because some of things are easier and shortcuts etc in language , but as i said it doesnt matter at all choose what you want to.
Ps . I started in vb.net and im still coding there , well even tho im not a pro i can comfortably read and write c# but i still love vb.net ( don't know , preferring writing Hex instead of conversions.touint16 , lol )
I'm going to state some facts and my opinion, but don't see this as criticism on your opinion, it's your opinion.
"Vb.net and c# are both .net languages so they look just similiar."
This isn't true. VB wasn't designed for the .Net framework but C# was.
Between these languages, there are many differences including keywords, operators, 'punctuation marks', etc.
However, since they both use .Net, the classes/modules/structs they use are the same.
(Not entirely since a My namespace is generated (or added?) in a VB.Net executable.)
"you should prefer vb.net because some of things are easier and shortcuts etc"
That's not really true imo.
Compare these code snippets:
VB.Net:
Code:
Imports System
Public Class Form1
Dim hello As String = "Hello" & ControlChars.NewLine & "World"
Private Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs) Handles Button1.Click
MessageBox.Show(hello)
End Sub
End Class
C#:
Code:
using System;
public class Form1
{
string hello = "Hello\nWorld";
private void Button1_Click(Object sender, EventArgs e)
{
MessageBox.Show(hello);
}
}
(Note that a little piece has to be added to the C# designer code to handle the event. The designer does this automatically, though.)
Specifying what to close ("End Sub"), using a keyword to pass as value ("ByVal"), not having character escaping ("\n" in C# and "& ControlChars.Newline &" in VB.Net makes your code a lot longer.
"but as i said it doesnt matter at all choose what you want to"
I beg to differ.
Since C# uses syntax similar to C, it's easier for C# coders to learn C, C++, Java, and other languages using C-like syntax.
If you want to stay with VB.Net or C#, which wouldn't be a bad choice imo, it of course does not matter since both languages have about the same functionality.
I'm going to state some facts and my opinion, but don't see this as criticism on your opinion, it's your opinion.
"Vb.net and c# are both .net languages so they look just similiar."
This isn't true. VB wasn't designed for the .Net framework but C# was.
Between these languages, there are many differences including keywords, operators, 'punctuation marks', etc.
However, since they both use .Net, the classes/modules/structs they use are the same.
(Not entirely since a My namespace is generated (or added?) in a VB.Net executable.)
"you should prefer vb.net because some of things are easier and shortcuts etc"
That's not really true imo.
Compare these code snippets:
VB.Net:
Code:
Imports System
Public Class Form1
Dim hello As String = "Hello" & ControlChars.NewLine & "World"
Private Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs) Handles Button1.Click
MessageBox.Show(hello)
End Sub
End Class
C#:
Code:
using System;
public class Form1
{
string hello = "Hello\nWorld";
private void Button1_Click(Object sender, EventArgs e)
{
MessageBox.Show(hello);
}
}
(Note that a little piece has to be added to the C# designer code to handle the event. The designer does this automatically, though.)
Specifying what to close ("End Sub"), using a keyword to pass as value ("ByVal"), not having character escaping ("\n" in C# and "& ControlChars.Newline &" in VB.Net makes your code a lot longer.
"but as i said it doesnt matter at all choose what you want to"
I beg to differ.
Since C# uses syntax similar to C, it's easier for C# coders to learn C, C++, Java, and other languages using C-like syntax.
If you want to stay with VB.Net or C#, which wouldn't be a bad choice imo, it of course does not matter since both languages have about the same functionality.
Nice. I wanna say something about this.
Im not very longer coding with vb.net less then a year , like 9-10 months.
I saw alot of open-source C# projects , even tho i just read them , i can write c# now also. writing "\n" instead of "vbNewLine" is not a big difference ^^ Also I think errors are more specific in vb.net
And this is how i make a "HelloWorld" messageboxer in vb.net :
Code:
Public Class Form1
Dim hello As String = "Hello" & vbNewLine & "World"
Private Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs) Handles Button1.Click
MsgBox(hello)
End Sub
End Class
The thing i want to say is , vb.net is more like english
Im not very longer coding with vb.net less then a year , like 9-10 months.
I saw alot of open-source C# projects , even tho i just read them , i can write c# now also. writing "\n" instead of "vbNewLine" is not a big difference ^^
Hehe, very true. For a small piece of const text, this is no problem.
But when handling or making large walls of text, it's really hard to read, imo.
For example, when you have a CLI application and you want a usage option, it's easier to do it like this: (...)
Code:
"MyApplication <0.1>\n
--help\tprint usage\n
--first\tdoes something\n
--second\t does something else\n"
(...), than to do it with vbNewLine and the tab ControlChar.
Quote:
Originally Posted by sarkoplata
Also I think errors are more specific in vb.net
I don't really understand what you mean there.
Could you give an example?
I don't really understand what you mean there.
Could you give an example?
Error list error texts , i mean , when you do something wrong , it appears in errorlist. I mean that error's list. [ even though most of exception texts are same ]
Btw, Case sensitive thingy makes C# hell for me . Also i just prefer writing
Code:
.tostring
for example and vb will make it ToString() for me
But in C# i should exactly write ToString()
Error list error texts , i mean , when you do something wrong , it appears in errorlist. I mean that error's list. [ even though most of exception texts are same ]
Pretty sure it's the same in VB.Net and C#.
Quote:
Originally Posted by sarkoplata
Btw, Case sensitive thingy makes C# hell for me . Also i just prefer writing
Code:
.tostring
for example and vb will make it ToString() for me
But in C# i should exactly write ToString()
It makes more stuff possible.
Example:
Code:
class MyClass
{
public int MyValue { get; set; }
public MyClass(int myValue)
{
MyValue = myValue;
}
}
You would need a keyword like "this" if you wasn't case sensitive.
