C# .NET - diffrence

Asked By matli radhakrishnareddy
04-Jun-08 08:13 AM
what 's diif b/w vb.net & c#.net

Syntax Differences and Managed and Unmanaged code difference  Syntax Differences and Managed and Unmanaged code difference

04-Jun-08 08:21 AM

refer the link, it explan u  http://www.geocities.com/gkmsr007/articles/CSharpVersusVBdotNET_Paper.htm#BK_1 and http://www.geocities.com/gkmsr007/articles/CSharpVersusVBdotNET_Paper.htm#BK_2 difference

http://www.geocities.com/gkmsr007/articles/CSharpVersusVBdotNET_Paper.htm

check this...  check this...

04-Jun-08 08:23 AM

Hi,

Here you can get the nice article

http://www.harding.edu/fmccown/vbnet_csharp_comparison.html

http://support.microsoft.com/kb/308470

http://www.dnzone.com/ShowDetail.asp?NewsId=21

`difference between C# and VB.NET  `difference between C# and VB.NET

04-Jun-08 08:28 AM
This MSDN link compares programming concepts, keywords, data types and operators in the 2 languages - http://msdn.microsoft.com/en-us/library/czz35az4(vs.71).aspx

Also check this 3 part series on the differences -
http://www.4guysfromrolla.com/ASPScripts/PrintPage.asp?REF=%2Fwebtech%2F012702%2D1%2Eshtml
http://www.4guysfromrolla.com/ASPScripts/PrintPage.asp?REF=%2Fwebtech%2F012702%2D1%2E2%2Eshtml
http://www.4guysfromrolla.com/ASPScripts/PrintPage.asp?REF=%2Fwebtech%2F012702%2D1%2E3%2Eshtml

Difference between VB.NET & C#.NET in various aspects.  Difference between VB.NET & C#.NET in various aspects.
04-Jun-08 08:44 AM

Although there are differences between Visual Basic .NET and Visual C# .NET, both are first-class programming languages that are based on the Microsoft .NET Framework, and they are equally powerful. Both Visual Basic .NET and Visual C# .NET use the common language runtime. There are almost no performance issues between Visual Basic .NET and Visual C# .NET. Visual C# .NET may have a few more "power" features such as handling unmanaged code, and Visual Basic .NET may be skewed a little toward ease of use by providing features such as late binding. However, the differences between Visual Basic .NET and Visual C# .NET are very small compared to what they were in earlier versions.

You have lot of articles to find out the differences b/w VB.NET & C#.NET depending on various aspects. Iam providing a few, which were discussed in different aspects. 

Go through them.

http://support.microsoft.com/kb/308470

some key syntactical differences between VB.NET (version 2) and C#. http://www.harding.edu/fmccown/vbnet_csharp_comparison.html

Choosing between C# and VB.NET: http://www.dnjonline.com/article.aspx?ID=mar05_vbvscsharp

Complete Comparison for VB.NET and C#: http://www.codeproject.com/KB/dotnet/vbnet_c__difference.aspx

http://p2p.wrox.com/topic.asp?TOPIC_ID=28722

The differences between C# and VB.NET: http://www.dnzone.com/ShowDetail.asp?NewsId=21

Hope this provides a good idea over the difference between VB.NET & C#.NET.

All the Best..!!

Rakesh Virkam.

Difference reply  Difference reply
04-Jun-08 11:50 AM

differences between Visual Basic .NET and Visual C# .NET, both are first-class programming languages that are based on the Microsoft .NET Framework, and they are equally powerful. Visual Basic .NET is a true object-oriented programming language that includes new and improved features such as inheritance, polymorphism, interfaces, and overloading. Both Visual Basic .NET and Visual C# .NET use the common language runtime. There are almost no performance issues between Visual Basic .NET and Visual C# .NET. Visual C# .NET may have a few more "power" features such as handling unmanaged code, and Visual Basic .NET may be skewed a little toward ease of use by providing features such as late binding.

However view this article

Language Equivalents
http://msdn2.microsoft.com/en-us/library/czz35az4(vs.71).aspx
reply difference  reply difference
04-Jun-08 11:55 AM

Check this:

Differences Between Microsoft Visual Basic .NET and Microsoft Visual C# .NET
http://support.microsoft.com/?kbid=308470

Don’t forget to do the download ;)

c# vs vb.net  c# vs vb.net
04-Jun-08 12:59 PM

couple of links from where you can get this info,

http://www.harding.edu/fmccown/vbnet_csharp_comparison.html

C# and VB.NET Comparison Cheat Sheet
http://aspalliance.com/625

 

 

difference between c# and vb.net  difference between c# and vb.net
04-Jun-08 02:59 PM
In general c# is more popular and can do many things which vb.net cannot. visual studio is also written in c# and c# is built specifically for the .net platform. See this article for more details on why c# is better http://weblogs.asp.net/bigyanr/archive/2008/02/07/is-vb-net-better-or-c-net-or-is-net-a-net-either-way.aspx
RE  RE
04-Jun-08 03:51 PM

Hello Matli

This is just a informative Microsoft first came up with the ASP which was never been popular and have many lacks in debugging and other functionalities so they decided up to get one platform which will give support to both favourite language.VB and C#

The basic difference in both of them is they are very much stick to their originalities though being in the .net platform means VB.NET still provides lots intellisense as comapre to C# where C# provides a powerful OOPS as to VB.NET

There are a lot difference in syntax in datatypes,functions,operators,namespaces,strings,arrays,loops
Out of which I will give you now Classes and Interface diff between them

You can get all the details by refering the Link Below.

VB.NET                                                   C#.NET

Accessibility keywords
Public
Private
Friend                   
Protected
Protected Friend
Shared

' Inheritance
Class FootballGame
  Inherits Competition
  ...
End Class 

' Interface definition
Interface IAlarmClock 
  ...
End Interface

// Extending an interface 
Interface IAlarmClock
  Inherits IClock
  ...
End Interface

// Interface implementation
Class WristWatch 
  Implements IAlarmClock, ITimer 
   ...
End Class 

Please refer this link

Accessibility keywords
public
private
internal
protected
protected internal
static

// Inheritance
class FootballGame : Competition {
  ...
}


// Interface definition

interface IAlarmClock {
  ...
}

// Extending an interface 
interface IAlarmClock : IClock {
  ...
}


// Interface implementation

class WristWatch : IAlarmClock, ITimer {
   ...
}

http://www.harding.edu/fmccown/vbnet_csharp_comparison.html

Happy Coding takecare

Nothing Major  Nothing Major
04-Jun-08 03:54 PM
For most purposes, there is no difference in their capabilities. If you have a VB background that you will be much faster at working in .Net if you use VB.Net.

If you come from a C++/Java background, you will feel more at home in C#.

The differences are primarily syntax based. There are not too many language capability differences and both are built on the CLR.

C# is considered to be more structured and disciplined, though that may be a matter of personal choice and style of coding.

I personally prefer C#.
Differences Between Visual Basic .NET and Visual C# .NET  Differences Between Visual Basic .NET and Visual C# .NET
05-Jun-08 12:40 AM

 

http://support.microsoft.com/kb/308470

You Can download the white papaer here:

http://download.microsoft.com/download/6/3/5/6354bf47-c597-4029-89e9-2495e7539ab9/vbcsharpwp.exe

Vb.net Vs c#  Vb.net Vs c#
05-Jun-08 01:06 AM

 

What are the advantages of C# over VB.NET and vice versa?

 

The choice between C# and VB.NET is largely one of subjective preference. Some people like C#'s terse syntax, others like VB.NET's natural language, case-insensitive approach. Both have access to the same framework libraries. Both will perform largely equivalently (with a few small differences which are unlikely to affect most people, assuming VB.NET is used with Option Strict on). Learning the .NET framework itself is a much bigger issue than learning either of the languages, and it's perfectly possible to become fluent in both - so don't worry too much about which to plump for. There are, however, a few actual differences which may affect your decision:

 

VB.NET Advantages

 

  • Support for optional parameters - very handy for some COM interoperability
  • Support for late binding with Option Strict off - type safety at compile time goes out of the window, but legacy libraries which don't have strongly typed interfaces become easier to use.
  • Support for named indexers (aka properties with parameters).
  • Various legacy VB functions (provided in the Microsoft.VisualBasic namespace, and can be used by other languages with a reference to the Microsoft.VisualBasic.dll). Many of these can be harmful to performance if used unwisely, however, and many people believe they should be avoided for the most part.
  • The with construct: it's a matter of debate as to whether this is an advantage or not, but it's certainly a difference.
  • Simpler (in expression - perhaps more complicated in understanding) event handling, where a method can declare that it handles an event, rather than the handler having to be set up in code.
  • The ability to implement interfaces with methods of different names. (Arguably this makes it harder to find the implementation of an interface, however.)
  • Catch ... When ... clauses, which allow exceptions to be filtered based on runtime expressions rather than just by type.
  • The VB.NET part of Visual Studio .NET compiles your code in the background. While this is considered an advantage for small projects, people creating very large projects have found that the IDE slows down considerably as the project gets larger.

 

C# Advantages

 

  • XML documentation generated from source code comments. (This is coming in VB.NET with Whidbey (the code name for the next version of Visual Studio and .NET), and there are tools which will do it with existing VB.NET code already.)
  • Operator overloading - again, coming to VB.NET in Whidbey.
  • Language support for unsigned types (you can use them from VB.NET, but they aren't in the language itself). Again, support for these is coming to VB.NET in Whidbey.
  • The using statement, which makes unmanaged resource disposal simple.
  • Explicit interface implementation, where an interface which is already implemented in a base class can be reimplemented separately in a derived class. Arguably this makes the class harder to understand, in the same way that member hiding normally does.
  • Unsafe code. This allows pointer arithmetic etc, and can improve performance in some situations. However, it is not to be used lightly, as a lot of the normal safety of C# is lost (as the name implies). Note that unsafe code is still managed code, i.e. it is compiled to IL, JITted, and run within the CLR.
  • Despite the fact that the above list appears to favour VB.NET (if you don't mind waiting for Whidbey), many people prefer C#'s terse syntax enough to make them use C# instead.

 

 

 I just got the above from a blog and seems to be good!

Here is the diff bet c# and vb.net  Here is the diff bet c# and vb.net
05-Jun-08 01:28 AM

VB.NET

C#

  • Support for optional parameters - very handy for some COM interoperability.
  • Support for late binding with Option Strict off - type safety at compile time goes out of the window, but legacy libraries which don't have strongly typed interfaces become easier to use.
  • Support for named indexers.
  • Various legacy VB functions (provided in the Microsoft.VisualBasic namespace, and can be used by other languages with a reference to the Microsoft.VisualBasic.dll). Many of these can be harmful to performance if used unwisely, however, and many people believe they should be avoided for the most part.
  • The with construct: it's a matter of debate as to whether this is an advantage or not, but it's certainly a difference.
  • Simpler (in expression - perhaps more complicated in understanding) event handling, where a method can declare that it handles an event, rather than the handler having to be set up in code.
  • The ability to implement interfaces with methods of different names. (Arguably this makes it harder to find the implementation of an interface, however.)
  • Catch ... When ... clauses, which allow exceptions to be filtered based on runtime expressions rather than just by type.
  • The VB.NET parts of Visual Studio .NET compiles your code in the background. While this is considered as an advantage for small projects, people creating very large projects have found that the IDE slows down considerably as the project gets larger.
  • XML documentation generated from source code comments. (This is coming in VB.NET with Whidbey (the code name for the next version of Visual Studio and .NET), and there are tools which will do it with existing VB.NET code already.)
  • Operator overloading - again, coming to VB.NET in Whidbey.
  • Language support for unsigned types (you can use them from VB.NET, but they aren't in the language itself). Again, support for these is coming to VB.NET in Whidbey.
  • The using statement, which makes unmanaged resource disposal simple.
  • Explicit interface implementation, where an interface which is already implemented in a base class can be re-implemented separately in a derived class. Arguably this makes the class harder to understand, in the same way that member hiding normally does.
  • Unsafe code. This allows pointer arithmetic etc, and can improve performance in some situations. However, it is not to be used lightly, as a lot of the normal safety of C# is lost (as the name implies). Note that unsafe code is still managed code, i.e., it is compiled to IL, JITted, and run within the CLR.

For differences of Kyeword, Data types, Operator etc just go thr this link;

http://www.codeproject.com/KB/dotnet/vbnet_c__difference.aspx

Also just go thr this link for more info;

http://www.harding.edu/fmccown/vbnet_csharp_comparison.html

Best Luck!!!!!!!!!!
Sujit.

Difference Vb.Net & C#  Difference Vb.Net & C#
05-Jun-08 07:14 AM

Both are first-class programming languages that are based on the Microsoft .NET Framework, and they are equally powerful. Visual Basic .NET is a true object-oriented programming language that includes new and improved features such as inheritance, polymorphism, interfaces, and overloading. Both Visual Basic .NET and Visual C# .NET use the common language runtime. There are almost no performance issues between Visual Basic .NET and Visual C# .NET. Visual C# .NET may have a few more "power" features such as handling unmanaged code, and Visual Basic .NET may be skewed a little toward ease of use by providing features such as late binding.

For syntax and datatype differences view the following article ::

http://

Create New Account
help
Is Visual Studio self-hosting ? .NET Framework Does Microsoft use Visual Studio IDE, Visual Studio Debugger, Visual Studio Linker and Visual Studio compiler for developing Visual Studio ? Or is Visual Studio not
Visual Studio .net .NET Framework Hi NG, ich habe vor längerer Zeit mit Visual Studio .Net 2003 gearbeitet und überlege momentan auf einen neueren Stand upzudaten. Ein Visual Studio .Net 2008 scheint es nicht zu geben. Habe zumindest mit googeln nichts gefunden. Was
Visual Studio versioning . . . . how to tell? .NET Framework To my knowledge, Visual studio 6 was released in 1998, then Visual Studio .NET 2002 is VS 7, then Visual Studio .NET 2003 is VS 7.1, then Visual
visual studio.net 2003 and Access 2007 database .NET Framework Hi I am currently using Visual Studio.Net 2003 running on Windows Server 2000 operating system. I have used Visual Studio.net 2003 connecting to Access 2002 databases in the pass with great success. Now
Wise for Visual Studio.NET Wise for Visual Studio.NET By Peter A. Bromberg, Ph.D. To "Print This Page" Link Peter Bromberg Wise for Visual Studio .NET is a total and complete installation development system for creating and editing Windows® Installer