Which one will be develop more from microsoft ???
VB.NET or VC# ??? or both ???
Will one of them be eliminated from Visual Studio ???
____________
Wille
Printable View
Which one will be develop more from microsoft ???
VB.NET or VC# ??? or both ???
Will one of them be eliminated from Visual Studio ???
____________
Wille
in a short time no..but in long time we dont know...a nuclear bomb can kill us tomorrow though so...go and see their sintax and see which is the one u most like :D
Well, I come from VB6. Surely, it will be more simpler to grow up my skill to VB.NET. :)
That's what I think. Dunno know if it's wrong.
But, lot of IT people here in Indonesia said that C# will grow more nd more. :p
__________
Wille
dunno..i prefer the vb sintax and i came from vb6 but theres ppl who prefer c# sintax
C# and VB.NET are virtually the same. Same coding structure, same data types, same objects, compiles exactly the same, even same IDE. The only difference is in basic syntax.
Also, its been decided that C# will be the standard for most 3rd party .NET compilers.
I've decided to learn VB.NET since I'm used to VB6. However, VB.NET is just soooo different. You really should treat it as a separate language. I had 3 years experience with VB6 (ie. making speech recognition programs, email programs, even a remote desktop program) but before I started learning VB.NET, I couldn't figure out how to make a stupid timer with it to test its speed. VB.NET does share some functions, however, with VB6, which will be somewhat helpful for the transition to .NET for VB6 programmers. Now, I'm making games with VB.NET, and have discovered that its up to 15x faster than VB6 (managed C++, C#, and VB.NET compile the same way, so they share the same functionality and speed).
Once you know 1 .NET language, you could probably learn another one over the weakend because their so similar. I'll bet I could achieve the same level of programming knowledge in C# as I currently do of VB.NET in just a couple of days of light studying.
So, basically, learn whichever language you want! It doesn't matter!
VB.NET and C# differ almost only in syntax, so whatever language you choose doesn't really matter.
I think 95 % of learning VB.NET or C# is learning the framework, which is exactly the same for VB.NET and C#.
So if you decide to learn the other language as well, you only have to learn the remaining 5%, and your done.
There are rumours from the microsoft camp that vb.net will be faded out in 5 yrs or so. I am using vb.net at the mo put trying to write more and more classes in c#. If you have no previous knowledge then def. learn c#. C# was designed for the .net platform. It offers great speed and stability in many areas.
C# and VB have exactly the same speed.
As for MS throwing out VB.Net after 5 years, I have to say "NOT A CHANCE" they tried to get rid of VB years and phase it into Java but did you know there are 3 million VB users and 1 millions C users. So I doubt they will cut of VB.Net, they may try but there will be so much VB code in use that they wont, unless they fancy loosing users of .Net.
I meant speed as in coding speed. C# has greater flexibility which often requires less code than vb.net with more consistent and easier-to-understand object handling.
As for the chances of fading vb.net out I think they will have a tough time also, but as i said its only a rumour!
You obviously don't know anything about VB.NET, so why are you saying bad about it?Quote:
Originally posted by cim3
I meant speed as in coding speed. C# has greater flexibility which often requires less code than vb.net with more consistent and easier-to-understand object handling.
As for the chances of fading vb.net out I think they will have a tough time also, but as i said its only a rumour!
C# and VB.NET are THE SAME! Only basic syntax differs! One does not have more flexibility, stability, functionality, or speed than another! Heck, I'll bet you can convert C# to VB line by line and vice versa.
You might as well say you want to learn .NET! As said before, 95% of learning a .NET language is learning the framework. When you program in C#, your actually just programming in .NET with the syntax of your choice, nothing more! There's no benefit of learning one over the other (C++.NET is different though, since its a lower-level language, and it allows you to write unmanaged, or non .NET, code)!
See, this is what has been wrong with describing .Net. It is too hard.
Obviously you haven't read up on C#. You can also write unmanaged code in C#. You can use pointers and such. Can't do that in VB.Net.Quote:
(C++.NET is different though, since its a lower-level language, and it allows you to write unmanaged, or non .NET, code)!
There are differences between the languages. VB.Net has a couple features that C# doesn't have, and C# has some stuff that VB doesn't have.
The thing I recommend is to go with either language. I personnally use C# for all my development, but have no problem using VB.Net because I am learning the framework either way. When it comes times to use a feature that isn't supported in the language your using (which will be in very rare instances), then jump over to the language that supports it and write a class in that language.
Quote:
Originally posted by hellswraith
Obviously you haven't read up on C#. You can also write unmanaged code in C#. You can use pointers and such. Can't do that in VB.Net.
Seriously?
Thats odd, the book I read, Beginning VB.NET (though its not much of a beginner-level book), published by syngress, says that C# doesn't support pointers (the 1st and 2nd chapters got into some detail of the other .NET languages)!
Then again, I've found several mistakes in that book as I read though it.
Ayecharumba, No Pimentos!!!!! The only good programming books I've read were from wrox!
I strongly suggest that everyone stays away from:
'Bible' books (ie Java Bible, for example)
Sams publishing books (learn *** in 21 hours)
and now, I'll add Syngress books to my list!
What is a pointer other then a memory address ? You can get round using pointers in VB. Heres a good example if your still not convinced about what will be the most used language.
Check out how many posts are in the VB.Net forum and now many in the C# forum :).
Hey ppl,
All of you must realize that some of us are dependent on coding for our bread and butter. It is not so much being all perfect sometimes on what and how you do it, but whether it can sell.
I have been coding, programming and developing in the commercial world for over 6 years. Tell you clients you use some kind of state of the art tech to code something and they wont even batter an eyelid. Its the end result that counts. If you cant deliver a project on time b4 a deadline, you can kiss your client and job goodbye.
Whatever it is, code in something you are comfortable with and get up to speed with whether its C#or VB or Managed C++. If you need to use pointers or operator overloading that C# can do, code that class in C# compile it and use it in your vb.net projects. You can do the same thing otherwise.
There are ppl out there (esp Java folks) who TEND to come from a academics background and believe the whole world MUST be perfect. Well, the whole world is NOT perfect, not even close and optimizing the use of an imperfect tool is sometimes better than just being OK with a perfect one. To illustrate, VB has always been a laughing stock amongst its Java and C++ peers over the years and I ADMIT that VB is COMPARATIVELY a more inferior language BUT how do you explain it being the most popular language in the world. Most corporates I work for, with and in has some form of VB running in their system. Sure, it might not be good enuf for mission-critical systems, but tell me how many ppl here codes mission-critical systems like a nuclear simulator ???
To sum up, being PRODUCTIVE is more important than being perfect. Making sure you reach point B is more important than how you get there. So if you are better with VB.NET to reach point B, use VB.NET, if you are better with C#, use it...Just make sure you reach where you want to go
AND if you still are insistent on learning the perfect .NET Language, I have the perfect solution for you >>> learn MSIL (Intermediate Language)
++++++++++++++++++++++++++
ï// PE Header:
// Subsystem: 00000003
// Native entry point address: 0000267e
// Image base: 11000000
// Section alignment: 00002000
// File alignment: 00000200
// Stack reserve size: 00100000
// Stack commit size: 00001000
// Directories: 00000010
// 0 [0 ] address [size] of Export Directory:
// 2624 [57 ] address [size] of Import Directory:
// 6000 [878 ] address [size] of Resource Directory:
// 0 [0 ] address [size] of Exception Directory:
// 0 [0 ] address [size] of Security Directory:
// 8000 [c ] address [size] of Base Relocation Table:
// 4000 [1c ] address [size] of Debug Directory:
// 0 [0 ] address [size] of Architecture Specific:
// 0 [0 ] address [size] of Global Pointer:
// 0 [0 ] address [size] of TLS Directory:
// 0 [0 ] address [size] of Load Config Directory:
// 0 [0 ] address [size] of Bound Import Directory:
// 2000 [8 ] address [size] of Import Address Table:
// 0 [0 ] address [size] of Delay Load IAT:
// 2008 [48 ] address [size] of CLR Header:
// Import Address Table
// mscoree.dll
// 00002000 Import Address Table
// 0000266e Import Name Table
// 0 time date stamp
// 0 Index of first forwarder reference
//
// 0 _CorExeMain
// 2050 [0 ] address [size] of Resources Directory:
// 0 [0 ] address [size] of Strong Name Signature:
// 0 [0 ] address [size] of CodeManager Table:
// 0 [0 ] address [size] of VTableFixups Directory:
// 0 [0 ] address [size] of Export Address Table:
// 0 [0 ] address [size] of Precompile Header:
// Code Manager Table:
// default
// Export Address Table Jumps:
// No data.
.assembly extern /*23000001*/ mscorlib
{
.publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4..
.ver 1:0:3300:0
}
.assembly extern /*23000002*/ Microsoft.VisualBasic
{
.publickeytoken = (B0 3F 5F 7F 11 D5 0A 3A ) // .?_....:
.ver 7:0:3300:0
}
.assembly extern /*23000003*/ System
{
.publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4..
.ver 1:0:3300:0
}
.assembly extern /*23000004*/ System.Data
{
.publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4..
.ver 1:0:3300:0
}
.assembly extern /*23000005*/ System.Xml
{
.publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4..
.ver 1:0:3300:0
}
.assembly /*20000001*/ ConsoleApplication1
{
.custom /*0C000002:0A000008*/ instance void [mscorlib/* 23000001 */]System.Reflection.AssemblyTrademarkAttribute/* 01000009 */::.ctor(string) /* 0A000008 */ = ( 01 00 00 00 00 )
// --- The following custom attribute is added automatically, do not uncomment -------
// .custom /*0C000003:0A000004*/ instance void [mscorlib/* 23000001 */]System.Diagnostics.DebuggableAttribute/* 01000005 */::.ctor(bool,
// bool) /* 0A000004 */ = ( 01 00 01 01 00 00 )
.custom /*0C000004:0A000006*/ instance void [mscorlib/* 23000001 */]System.Runtime.InteropServices.GuidAttribute/* 01000007 */::.ctor(string) /* 0A000006 */ = ( 01 00 24 36 41 41 45 32 34 33 30 2D 34 37 35 46 // ..$6AAE2430-475F
2D 34 41 38 32 2D 41 31 35 36 2D 45 41 42 39 36 // -4A82-A156-EAB96
42 33 43 44 36 41 32 00 00 ) // B3CD6A2..
.custom /*0C000005:0A000007*/ instance void [mscorlib/* 23000001 */]System.CLSCompliantAttribute/* 01000008 */::.ctor(bool) /* 0A000007 */ = ( 01 00 01 00 00 )
.custom /*0C000006:0A00000A*/ instance void [mscorlib/* 23000001 */]System.Reflection.AssemblyProductAttribute/* 0100000B */::.ctor(string) /* 0A00000A */ = ( 01 00 00 00 00 )
.custom /*0C000007:0A000009*/ instance void [mscorlib/* 23000001 */]System.Reflection.AssemblyCopyrightAttribute/* 0100000A */::.ctor(string) /* 0A000009 */ = ( 01 00 00 00 00 )
.custom /*0C000008:0A00000B*/ instance void [mscorlib/* 23000001 */]System.Reflection.AssemblyCompanyAttribute/* 0100000C */::.ctor(string) /* 0A00000B */ = ( 01 00 00 00 00 )
.custom /*0C000009:0A00000C*/ instance void [mscorlib/* 23000001 */]System.Reflection.AssemblyDescriptionAttribute/* 0100000D */::.ctor(string) /* 0A00000C */ = ( 01 00 00 00 00 )
.custom /*0C00000A:0A00000D*/ instance void [mscorlib/* 23000001 */]System.Reflection.AssemblyTitleAttribute/* 0100000E */::.ctor(string) /* 0A00000D */ = ( 01 00 00 00 00 )
.hash algorithm 0x00008004
.ver 1:0:987:33023
}
.module ConsoleApplication1.exe
// MVID: {5804AB25-DC77-4E4D-9C36-00A616BAB595}
.imagebase 0x11000000
.subsystem 0x00000003
.file alignment 512
.corflags 0x00000001
.namespace ConsoleApplication1
{
.class /*02000002*/ private auto ansi sealed Module1
extends [mscorlib/* 23000001 */]System.Object/* 01000001 */
{
}
// note that class flags, 'extends' and 'implements' clauses
// are provided here for information only
.namespace ConsoleApplication1
{
.class /*02000002*/ private auto ansi sealed Module1
extends [mscorlib/* 23000001 */]System.Object/* 01000001 */
{
.custom /*0C00000B:0A000002*/ instance void [Microsoft.VisualBasic/* 23000002 */]Microsoft.VisualBasic.CompilerServices.StandardModuleAttribute/* 01000003 */::.ctor() /* 0A000002 */ = ( 01 00 00 00 )
.method /*06000001*/ public static void
Main() cil managed
// SIG: 00 00 01
{
.entrypoint
.custom /*0C000001:0A000003*/ instance void [mscorlib/* 23000001 */]System.STAThreadAttribute/* 01000004 */::.ctor() /* 0A000003 */ = ( 01 00 00 00 )
// Method begins at RVA 0x2050
// Code size 14 (0xe)
.maxstack 8
.language '{3A12D0B8-C26C-11D0-B442-00A0244A1DD2}', '{994B45C4-E6E9-11D2-903F-00C04FA302A1}', '{00000000-0000-0000-0000-000000000000}'
// Source File 'D:\VSNET Projects\ConsoleApplication1\Module1.vb'
.line 3:5 'D:\\VSNET Projects\\ConsoleApplication1\\Module1.vb'
//000003: Sub Main()
IL_0000: /* 00 | */ nop
.line 4:7
//000004: Console.WriteLine("To all .NET Folks, why not you stop bickering over which language is better and learn the .NET Framework instead")
IL_0001: /* 72 | (70)000001 */ ldstr "To all .NET Folks, why not you stop bickering over"
+ " which language is better and learn the .NET Framework instead" /* 70000001 */
IL_0006: /* 28 | (0A)000001 */ call void [mscorlib/* 23000001 */]System.Console/* 01000002 */::WriteLine(string) /* 0A000001 */
IL_000b: /* 00 | */ nop
.line 5:5
//000005: End Sub
IL_000c: /* 00 | */ nop
IL_000d: /* 2A | */ ret
++++++++++++++++++++++++++
Im a senior software developer (sounds good eh?) and agree with SoftwareMaker on many points. I have good arguments with my boss about how keeping the perfect code, its his job to get it done and its my job to get it done perfect. I just argue for as long as possible to try and get the best out of the time, and the type of customers we deal with want nearly mission critical systems (automated backup for banks/councils etc) so they have to be good.
If you just want to get into .Net go with what you know, VB or C.
If you know neither then VB is easy syntax to pick up, and IMO will not go out of fashion for a long long time.
Those are my points. Use whatever language you feel more comfortable with. You should really get familiar with both VB.Net and C#; it will only help you in the long run when you do need to switch back and forth. To me it has been great. I can take an example in C# and easily convert it to VB, and vice versa.
That statement doesn't work. Think about where you are. You are at VBforums. Of course there is going to be more activity in the VB.Net section than the C# one. If you want to see some C# forums that are even more active than this VB.net one, then you can go to sites that cater more to C#. Example:Quote:
Check out how many posts are in the VB.Net forum and now many in the C# forum
www.c-sharpcorner.com
www.gotdotnet.com
Apakabar dari Indonesia !!!
My point of view is no matter what language you learn or use as long as you can master it. All langauges are the same none of it are easy. When you write a real program all will become difficult.
VB .net will not disapear over night which I am sure! By the way, after I test both VB and C# I think I perfer VB .net more then C#. once you learn it you know ASP .net, VBA, VBScript already since they are so similar.
Suppose u have 2 companies X and Y and If someone asks u which company u want to develop more.. Then, Ur answer will be both. Microsoft or any other organisation wants to develop all their products, but the users are the one who make final decision. VB is more popular for its simplicity and VC for its performance. Therefore, Its a competition for the simplicity and the performance and nothing else.... That's all........
Prashanth
You have it wrong.Quote:
Originally posted by getprashanth
Suppose u have 2 companies X and Y and If someone asks u which company u want to develop more.. Then, Ur answer will be both. Microsoft or any other organisation wants to develop all their products, but the users are the one who make final decision. VB is more popular for its simplicity and VC for its performance. Therefore, Its a competition for the simplicity and the performance and nothing else.... That's all........
Prashanth
For .NET assemblies, VB, C#, and C++.NET compile the same way, so they share the same functionality and speed.
Its just a matter of which syntax you prefer, no other difference.
See the background first...
I am Software Engineer working on VB.Net, I have an experience of 3 years in VB.6.0, I have been selected for the present VB.Net post because of my experience in VB6.0, since they felt that, It will be easy for me to work on VB.Net..
So, When you are arguing upon the development of Microsoft technologies VB.Net and VC#, Why don't u consider their origin ??? VB.Net has not emerged on its own., Remember that VB6.0 is its base (Atleast in its syntax), similarly for others too. And when a person or organization opts for development on a specific technology (like VB.Net) , there is a lot of chance that they are following the earlier versions of that technology before they start working on the new technology. One has to remember that fact. I agree upon ur argument that, for .NET assemblies - VB, C#, and C++.NET compile the same way, so they share the same functionality and speed and everyone knows that. But that's not the whole....
wrong again:D same performance.... benchmarks show that too, it's not just talking about a theoryQuote:
Originally posted by getprashanth
See the background first...
When you are arguing upon the development of Microsoft technologies VB.Net and VC#, Why don't u consider their origin ??? VB.Net has not emerged on its own., Remember that VB6.0 is its base (Atleast in its syntax), similarly for others too. And when a person or organization opts for development on a specific technology (like VB.Net) , there is a lot of chance that they are following the earlier versions of that technology before they work on the new technology. You have to remember that fact. I agree to ur argument that, For .NET assemblies, VB, C#, and C++.NET compile the same way, so they share the same functionality and speed. But that's not the whole....
I really cant believe you are still arguing abt this topic. The will never cease as programmers are essentially egoistical ppl who swear by whatever you use. We are creatures of comfort by nature and tend to stick to something we are familiar with. But the world changes and we, as code warriors must learn to change too. SmartER Java programmers might pick up VC#.NET to hedge themselves againt the fortunes of SUN, the others will always be at their forums bickering and bitching with each other why Java is better and why they will never learn another language. If you are still a cobol pascal programmer who is stubborn and egoistical (like me years ago :)), I would be begging for food now.
essentially, there will always be Java against VB, Java against VC++, VB.NET against VC#, VC# against VC++. It will never stop. Different languages are created that way with different longs and shorts for different users and purposes. While everyone is fighting, the vendors like MS and SUN are laughing. We are paying them $$$ to fight like kids what to use in their camp.
If you havent realized it by now, how the fortunes of the languages turn out is not at the mercy of us ppl but by the vendors and creators of the languages (esp their marketing team)
There are many many good languages out there that never made it due to the fortunes of their vendors. Smalltalk is a good example of a gr8 language that got nowhere.
Read my earlier post in this thread and the other posts you will also realize that the senior developers are the ones who know that getting the job done to be delievered on time so we get paid instead $$$ is the most important. I repeat GETTING to point B is more important than HOW you get there. Ultimately, we are service providers, using a tool and our time to make money. And that tool should be contained like a carpenter's toolbox where different tools are used for different purposes. Remember, we are not paid by what tools we use, but if we deliver at all.
Unless MS is paying you to brag abt their tools here, I suggest each programmer arm themselves with whatever is needed to get the job done, regardless of the tools used
And for the still very egoistical .NET programmer out there who believes the world must be perfect, i repeat what I have said in my earlier post
LEARN MSIL (Intermediat Language). Every .NET language compiles down to that !!!
For those who are sick abt arguing what .NET language to use, please post a STOP ARGUING in your post here to signify others to stop arguing and learn something different. Learning another language can only be good...
STOP ARGUING
wrong again same performance.... benchmarks show that too, it's not just talking about a theory
__________________
Mr. Polite, Be Polite
Where are u??? Pls. read my post again and reply.., Kindly come out of ur dreams, Its a forum and not ur hand phone to talk as u like. Be polite.. and Read and reply ... U r a kid and act like a kid., Don't be too smart...
ahem
:eek:
:rolleyes:
:o
:p
well
I guess the discussion is going to far. I don't think it will be good to show off here. What I need to know is whether VB or C# be developed more, since I've see that the concept of VB.NET nd C# is almost the same. I thought, Microsoft will eliminate one of them someday in the future, considering bout the pros nd cons on maintain both language which have the same concept, speed, performance, etc....
I think, we better stop the discussion till here.
Thx for all...
_____________
Wille