jeremy6996
11-12-2006, 03:52 AM
Wich one of thease languages are first of all better for makeing remote assist and secondly whut are the disadvantages and advatages
View Full Version : C#.....vb.net
dave_
11-12-2006, 04:15 AM
1. Please run you posts through a spell checker.
2. Thats a valid question, but not a good one; you can easily find the answer on google. For example look for Visual Basic vs C# (http://www.google.co.uk/search?sourceid=mozclient&ie=utf-8&oe=utf-8&q=visual+basic+vs+c%23)
2. Thats a valid question, but not a good one; you can easily find the answer on google. For example look for Visual Basic vs C# (http://www.google.co.uk/search?sourceid=mozclient&ie=utf-8&oe=utf-8&q=visual+basic+vs+c%23)
jeremy6996
11-12-2006, 12:52 PM
ok, but i alredy tryed that and im trying to find the network programming, like wich one of the diffrent languages will be good for network programming,sending packets opening sockets that stuff would be good for it,
bu thanks for the segestion
bu thanks for the segestion
Reedbeta
11-12-2006, 02:21 PM
Jeremy, both are .NET languages and so both have exactly the same capabilities as regards network programming (and everything else). You should choose based on which language you like more.
jeremy6996
11-12-2006, 11:22 PM
They must have a something thats diffrent
juhnu
11-13-2006, 12:22 AM
Jeremy, I really wish you paid more attention to correct spelling and punctuation..
Reedbeta
11-13-2006, 09:37 AM
They must have a something thats diffrent
Their syntax is different. That's about all.
Their syntax is different. That's about all.
daviangel
11-13-2006, 07:14 PM
Which one is better is like saying is a moneywrench or a regular wrench better for tightening a bolt?
Anyways here the technical nitty gritty you asked for:
C# features advantages
* Supports unsafe code blocks for improved performance at the expense of not being verifiable as "safe" by the runtime
* Operator overloading (not available in VB prior to 2005)
* Iterators (C# 2.0)
* Anonymous methods (C# 2.0)
* Nullable structures are fully supported with the ? notation (C# 2.0)
[edit] Visual Basic .NET advantages
* With keyword for using the same object repeatedly (this feature was intentionally not added to C# [1])
* Named indexers (essentially, properties that take arguments)
* Partial compatibility with legacy Visual Basic code
* The My namespace, which simplifies the use of many framework classes by encapsulating their functionality in a flatter, more accessible structure
* More granularity with exception handling with the Catch…When clause, which allows for custom exception filters
* The Handles keyword allows declarative wiring of events to functions; Imperative (C# style) event wiring is also available.
* Language support for late-binding (can be turned off with an Option Strict declaration)
* Optionally ignore ref/ByRef behavior for passing arguments. (C# requires a temp variable to do this.)
* Optional parameter support is useful when using COM automation. This is especially important when working with Microsoft Office.
http://en.wikipedia.org/wiki/Comparison_of_C_sharp_and_Visual_Basic_.NET
So as you can see there are only like 3 things you can do in C# you can't do in VB and alot of more things you can do with VB that you cannot in C# so you decide!
Anyways here the technical nitty gritty you asked for:
C# features advantages
* Supports unsafe code blocks for improved performance at the expense of not being verifiable as "safe" by the runtime
* Operator overloading (not available in VB prior to 2005)
* Iterators (C# 2.0)
* Anonymous methods (C# 2.0)
* Nullable structures are fully supported with the ? notation (C# 2.0)
[edit] Visual Basic .NET advantages
* With keyword for using the same object repeatedly (this feature was intentionally not added to C# [1])
* Named indexers (essentially, properties that take arguments)
* Partial compatibility with legacy Visual Basic code
* The My namespace, which simplifies the use of many framework classes by encapsulating their functionality in a flatter, more accessible structure
* More granularity with exception handling with the Catch…When clause, which allows for custom exception filters
* The Handles keyword allows declarative wiring of events to functions; Imperative (C# style) event wiring is also available.
* Language support for late-binding (can be turned off with an Option Strict declaration)
* Optionally ignore ref/ByRef behavior for passing arguments. (C# requires a temp variable to do this.)
* Optional parameter support is useful when using COM automation. This is especially important when working with Microsoft Office.
http://en.wikipedia.org/wiki/Comparison_of_C_sharp_and_Visual_Basic_.NET
So as you can see there are only like 3 things you can do in C# you can't do in VB and alot of more things you can do with VB that you cannot in C# so you decide!
Reedbeta
11-13-2006, 07:52 PM
I think it should be pointed out that all these differences are syntactic sugar, i.e. there's really nothing that can be done in one that can't be done in the other, only things that are slightly more convenient in one than the other.
The same article states that "the biggest difference between the two languages, is not the language, but the developer. Many (if not most) .NET developers came from either the VB environment, or the C/C++ environment. These two groups had very different coding standards, best practices, etc."
The two languages encourage somewhat different styles of writing code because of the different cultures of the developers. If you used any version of Basic before, go ahead and learn VB.NET. If you used C, C++ Java, PHP, or any other language based on C-syntax before, then go ahead and learn C#. If you haven't learned any of these before then I would recommend C# as knowing that syntax will give you a head start if you then want to learn another popular programming language like C++ or Java.
The same article states that "the biggest difference between the two languages, is not the language, but the developer. Many (if not most) .NET developers came from either the VB environment, or the C/C++ environment. These two groups had very different coding standards, best practices, etc."
The two languages encourage somewhat different styles of writing code because of the different cultures of the developers. If you used any version of Basic before, go ahead and learn VB.NET. If you used C, C++ Java, PHP, or any other language based on C-syntax before, then go ahead and learn C#. If you haven't learned any of these before then I would recommend C# as knowing that syntax will give you a head start if you then want to learn another popular programming language like C++ or Java.
daviangel
11-13-2006, 08:00 PM
Personally I find myself using VB alot more lately since the VS2005 IDE does alot of the work for me with code completion and not having to type a semicolon at the end of each line is refreshing.
I use C# when I have to though since alot of book I own covering managed DX use it but I find myself easily porting over the C# code to VB if the code is not already available on the CD that comes with the book.
And having uses VB6,C,C++,Java in the past I can see where it'd be easier to pick up C# coming from c,c++,java since they all use curly braces.
On the other hand past VB users and delphi,pascal user will find VB.NET more familiar with no need to end statements with ; and no need for {}.
I use C# when I have to though since alot of book I own covering managed DX use it but I find myself easily porting over the C# code to VB if the code is not already available on the CD that comes with the book.
And having uses VB6,C,C++,Java in the past I can see where it'd be easier to pick up C# coming from c,c++,java since they all use curly braces.
On the other hand past VB users and delphi,pascal user will find VB.NET more familiar with no need to end statements with ; and no need for {}.
vBulletin, Copyright ©2000-2010, Jelsoft Enterprises Ltd.