VB.NET or C#
Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: General Discussion
Forum Description: General discussion and chat on any topic.
URL: https://forums.webwiz.net/forum_posts.asp?TID=11970
Printed Date: 01 April 2026 at 1:42pm Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: VB.NET or C#
Posted By: Amateur
Subject: VB.NET or C#
Date Posted: 28 September 2004 at 11:25am
|
Is there a big difference between VB.NET & C#? Its just that i have been learning myself C# from a book i bought. Now back at college we are start doing VB.NET. So was wondering if i should stop learning the C# and buy another book about VB.NET? Both being used in connection to ASP.NET.
|
Replies:
Posted By: michael
Date Posted: 28 September 2004 at 11:39am
sure there is a big difference, both are seperate languages, thus if you know c# you know the classes of the .net framework which will make it easy for you to learn vb.net.
I would not stop learning c# if you are at it, just do both.
------------- http://baumannphoto.com" rel="nofollow - Blog | http://mpgtracker.com" rel="nofollow - MPG Tracker
|
Posted By: theSCIENTIST
Date Posted: 03 October 2004 at 7:05pm
Put simple, yes, it's different languages, and it's usually down to your programming background, C# comes from C and VB.NET from VB.
I personally prefer VB, can't stand the voids in C# so I always avoid the voids :) and all those ; at the end of lines, but if you are following a book on C# and feel confortable with the syntax, go for it.
Following michaels advice, I can further add that it can be useful for you at this stage to look at two files (C# and VB.NET) that do the same, and look at the code to determine which one strikes you the most, which one are you more confortable with, this will cut the ammount of time you will take to learn and master.
------------- :: http://www.mylittlehost.com/ - www.mylittlehost.com
|
Posted By: xeerex
Date Posted: 03 October 2004 at 9:19pm
I'm not a programmer, but I do the web development for a decent sized
software app community that uses C#. One of the things to be aware of
if you are worried about protecting your code is the fact that .NET is
very easy to decompile using any of several available online
decompilers. Here's a quote from an eBook from desaware.com that we
puchased concerning this issue:
www.desaware.com wrote:
Did you know that you actually ship your source code every time you
distribute a .NET assembly? And you may not even realize it. One of the
consequences of the architecture of .NET is that a great deal of
information about an assembly is kept with the assembly in a part of
the file called the Manifest. This information makes it remarkably easy
to not just recompile the assembly, but to decompile it, make
modifications, then recompile it. While such reverse engineering has
always been possible, it is extraordinarily easy with .NET - a
situation that is a significant problem to anyone distributing .NET
applications or components who is concerned about protecting their
intellectual property. |
And another quote [ http://aspnet.4guysfromrolla.com/articles/080404-1.aspx - here ]:
4guysfromrolla.com Decompiling .NET Assemblies wrote:
When you compile a .NET application, the source code is translated into MSIL in a fairly straightforward manner. That is,
there is a rough symmetry between a line of C# code, and the resulting MSIL. Since there is a rough mapping between high-level
code and MSIL, it is possible to take an assembly's MSIL and convert it back to equivalent C# or VB.NET code. In fact,
there are free programs that exist that do this very thing! |
Here is a link to a trial decompiler:
http://www.remotesoft.com/salamander - http://www.remotesoft.com/salamander
And a link to a popular free one called Reflector:
http://www.aisto.com/roeder/dotnet/ - http://www.aisto.com/roeder/dotnet
------------- http://webspacegeeks.com - Need Hosting, Domains, Dedicated Servers?
http://www.smartergeek.com - web design | pc support | training | podcasts | video production
|
Posted By: Mart
Date Posted: 04 October 2004 at 2:13am
|
You cannot "disassemble" a .NET app if you went over it with a decent obfuscator.
|
|