Share via


Why so many examples in Visual Basic?

I've received a few queries lately as to why MSDN - and Microsoft as a whole - has become more focused on producing Visual Basic.NET examples and code snippets in our articles and presentations. The reason is two-fold.

First, while I can't publicly state the actual numbers, I can tell you that there are many times more Visual Basic developers than C++ and C# developers. Therefore, basic business sense would indicate that - since it's not economically efficient to produce examples in all languages - we produce examples in the language used by the majority of developers using our platforms.

Second, we've spent a good deal of time and money evaluating how each group of programmers reacts to articles and presentations when the code is in the another language. These statistics show that the majority of C++ and C# developers are more apt to read an article that contains Visual Basic.NET material than the reverse. In other words, a very high percentage of Visual Basic developers will not read an article if it contains C++ or C#.

I'll leave trying to surmise why this is true to the reader. However, my personal opinion is that C++ and C# developers are much more accustomed to class libraries than Visual Basic developers. As a result, they can more easily look past the exact language semantics of a .NET example written in Visual Basic and focus instead on the .NET types/classes being used. Visual Basic developers - on the other hand - coming from a less object-oriented background of Visual Basic 6, already have the learning curve of trying to learn a new way of developing software without the added overhead of also having to convert the language syntax.

Whatever the reasons for this phenomenon, our research has shown that producing examples for presentations and articles in Visual Basic enables the broadest reach to all of our developers.

Comments

  • Anonymous
    November 21, 2005
    As a C# developer, I really don't like seeing examples in VB. While I can typically understand a VB example, I often like to copy-and-paste sample code and try it out, to experiment and learn about the technique. If the code is in VB, that is a lot less useful.

  • Anonymous
    November 21, 2005
    tzagotta, you actually just made the point. While you don't like the VB examples, you can still function with them and convert them. In our studies, the majority of VB programmers won't even read the article if it has C# or C++. Therefore, it's really a case of the following:

    * We can have a much smaller percentage of programmers (C#/C++) not like the fact that it's VB, but they will read and find the article ultimately useful after converting the code

    or

    * We can have a very large percentage of the programmers (VB) not even read the article

    This is ultimately why we decided to post in mainly VB.

  • Anonymous
    November 21, 2005
    There are community sites to transform VB->C# and vice versa. MSFT should operate such site offcially on MSDN web and put links to tranlsate the example on-the-fly within the its text. Providing just single langugage would be then enough !

  • Anonymous
    November 21, 2005
    Tom, sure, I can convert VB to C# and vice-versa (just as any VB programmer could), but my point is that if the example is in VB, it takes me 10x as long to use because of the need to do the conversion, and I usually figure it is not worth the time.

    For some context, I am thinking more about code examples that are say 50-150 LOC. Really short examples are not an issue, but those tend to not be as helpful as the longer examples.

    Pazu's idea of automatic conversion is a good idea. Otherwise, I think that MS should be committed to providing most examples in its top 3-4 supported languages, e.g., VB, C#, C++, and maybe J# (not sure about the popularity of the last one).

  • Anonymous
    November 21, 2005
    Pazu, it's not nearly so simple.

    That's like saying we don't need to localize our Dev Centers because someone can put them through babelfish. Sure, you can convert simple sentences, but not complex sentences, paragraphs and articles. When you attempt to do so, the text get mostly converted to the target language. But it's grammar is poor and the much of the original meaning is lost.

    Likewise, you can easily convert one .NET programming language to another when it involves simple tasks like making calls to methods/functions. However, when it gets more involved than that, there are specific, subjective ways to properly code in a given language that are much too complex to put into a translator.

    Just ask anyone that performs the task of coverting or migrating systems from one language to another and they'll tell you the task is not as easy as it seems.

  • Anonymous
    November 21, 2005
    The comment has been removed

  • Anonymous
    November 21, 2005
    Thanks guys for all the great feedback, but this conversation is turning from "Why VB examples?" to "Why not all languages?"

    I will say that we're actively working on:

    1) Getting authors to submit samples in both VB and C#
    2) Investigating options regarding providing multiple langauges.

    However, for the time being when the article has to show a single language, I hope that I've answered the question as to why that language will generally be VB.

  • Anonymous
    November 21, 2005
    tangent - the point about there being more vb.net developers is troubling to me, as a look at most .net job boards indicates an employer preference for c#.

  • Anonymous
    November 21, 2005
    Well, any good coder can fairly easily read c# or vb.net code and understand what's up. If it were up to me, I'd use c#, but my company's apps are vb.net.

    Seems to me for the past 4 years most code samples have been in c#. Nice to see the change.

  • Anonymous
    November 22, 2005
    > 1) Getting authors to submit samples in both VB and C#
    > 2) Investigating options regarding providing multiple langauges.

    # 1 sort of belies MS's claim that under VS2005, C++/CLI is a "first rate" language for .NET devekopment. See the discussion in
    http://blogs.msdn.com/texblog/archive/2005/11/21/495404.aspx
    I therefore hope more attention will be given to # 2.

  • Anonymous
    November 22, 2005
    I agree, in that I use both c# and vb.net depending on what I am asked for. The language it'self is one of preference. If any potential member of my development team have a problem understanding the gist of sample code in either language I wouldn't employ them.

    I hear that vb.net developers outnumber c# developers 3 to 1 or more, so by all means publish code in vb.net

    Most important to me is to be able to find good solutions to problems written in managed code, and there are getting to be mre all the time.

    Good work guys.

  • Anonymous
    November 22, 2005
    I am predominantly a VB programmer but actually prefer my examples in C#, as it forces me to convert the code and hence take the time to dissect it. If I get VB code it is just too tempting just to copy and paste it.

  • Anonymous
    November 23, 2005
    The comment has been removed

  • Anonymous
    November 23, 2005
    VB.net originates from VB 6.5.4.3.2.1 i.e. the first version of VB was just BASIC since that time microsoft is developing naturally the consideration will be more on visual basic

  • Anonymous
    November 23, 2005
    VB.net originates from VB 6.5.4.3.2.1 i.e. the first version of VB was just BASIC since that time microsoft is developing naturally the consideration will be more on visual basic

  • Anonymous
    November 24, 2005
    Wow! Thats exactly the way I am, I will not even bother reading C# or C++ articles, but I will read VB examples, since I know how it works and at the time being is the only language I know, so I figure ahhh.. whatever I'll come back to this article when I know C# but otherwise i won't even bother.. Good Work! Thanks for the VB CODE!!

  • Anonymous
    November 24, 2005
    Well... Does Microsoft want to tell me that I can do in VB everything I can do in C++ ? Or vice versa ? The answer is no.
    If the samples are in VB or C#... OK... but the C++ samples are missing. That's the point.
    I'm still working in C++ because I can't do what I want to do with C# ou VB. These are different languages targeting different needs. If I use C++, this is because I can't use C# or VB.
    You say "there are many times more Visual Basic developers than C++ and C# developers". But how many times more software released in C++ than in C# ou VB ?

  • Anonymous
    November 25, 2005
    I'm really happy to see more VB. C# has been the fresh new language from Microsoft and the media darling. Even though there are millions and millions of Visal Basic developers out there the editors at MSDN have chosen to favor C# in the majority of articles written in the last couple years.

    If most developers prefer to read articles written with their preferred language (and skip articles written in the other language -- as many have said in the comments) then it makes economic sense for Microsoft to solicit articles in the more popular language (VB).

  • Anonymous
    November 25, 2005
    I don't think arguments such as 3:1 ratio of VB to C# programmers means anything. There is enough of each to need to cater for both.
    The thing to remember about including a C# example is that it effectively expands the casual readership to not only C++, but also J#/java, and javascript, since the syntax is so close.

  • Anonymous
    November 26, 2005
    Thanks Tom,

    I was wondering why it's the way it is too. I hear a lot of gripes and groans, and as a C#er I'd rather see C# examples myself, but honestly, I think it's for the better that examples be written in VB.

    I don't mean this in a bad way, but the rest of us are more adept at reading code in other languages - that includes C++ers and Javaers.

  • Anonymous
    November 27, 2005
    The comment has been removed

  • Anonymous
    November 27, 2005
    There's one that translates from code here: http://authors.aspalliance.com/aldotnet/examples/translate.aspx

    The problem with this is that there's no guarantee that the translated code will be correct, much less will it be canonical. Cleaning up code like that is as mundane and uncertain as fixing bugs.

    Converting from a compiled assembly doesn't work either, because the compiler optimizes the code and makes it less legible than the original (try Lutz Roeder's Reflector). It also omits comments and formatting, which is crucial to documentation code.

    Sure, either might be "good enough" in a lot of cases, but to professional documentation authors, "good enough" isn't good enough.

  • Anonymous
    November 28, 2005
    So, most people that are VB, don't want anything to do with C++ right, because they dont want to translate the language? maby there is some way to develope a program that would help with this process of Translating different programming languages to the needed one. Is this Possible Tom?

  • Anonymous
    November 28, 2005
    Developing samples and documentation in JUST Visual Basic is an excuse, not a solution. As a developer who works in both VB and C#, I can tell you that I prefer the examples to be in both languages.

    There is nothing more frusturating than translating 1,000s of lines of VB into C# so that I can demonstrate something to our staff which write mostly in C# and C++.

    If Microsoft is no longer committing itself as heavily to the C# language, maybe it's time we looked into moving back towards Java (guess what Java examples are written in? yup, you guessed it, Java!).

  • Anonymous
    November 28, 2005
    I don't buy the '3 to 1' argument either. I find it hard to believe that an a company with your resources can't or won't be bothered to have C# examples.

    Your argument is really along the lines of "We'll hope the C# coders will be flattered that we consider them smarter than VB coders they'll take on examples conversion as a challenge rather than a hindrance".

    I'm a C# programmer with a C++ background, and there's enough pressure in development without having to do a conversion that for the longer examples may take a considerable time in itself to convert and debug.

    By not providing the C# you're showing you either don't have the resources (unlikely for MS) or you have some grand scheme to subliminally turn people away from C#, in the same way you put out J# to muddy and confuse the Java community: ie. get a competitor out there, then slowly wither support for it.

  • Anonymous
    November 28, 2005
    As primarily a standard C++ user, a lot of the sample code can be tough to parse. Thing like using GDIPlus or database calls are not such straightforward translations. I do think that C# and VB code sample are roughly interchangeable.

    Again, if the translations are so simple that you expect the reader to perform them, why couldn't the author likewise perform them. Alternatively, you could allow readers to type in and comment on code samples from other languages. Even if they weren't official Microsoft sactioned code samples they would still be useful.

  • Anonymous
    November 29, 2005
    Can we have the exmples in MSIL? All developers on .Net should understand it and it's language agnostic... ;)

    Cheers!

  • Anonymous
    November 29, 2005
    It would be cool if Visual Studio could switch language on the fly...
    Like, if I have a codefile written in VB, I could click the button "Switch to C#", or something like that :)

  • Anonymous
    November 30, 2005
    Why did you guys bother to introduce C# if in the end you start whining about MSDN support. C++ and VB would probably be enough to cover everything. When you say C# you mean .NET. When you say VB or C++ you will need to think twice. Why not create all samples in C# if it is .NET.

  • Anonymous
    December 01, 2005
    Visual basic is the best language anyway. Why use C++ or C#?

  • Anonymous
    December 01, 2005
    The comment has been removed

  • Anonymous
    December 01, 2005
    While examples are in VB it would be nice to know how things are transfered to a C level Code. I use both C++ simple COM object to get the speed i need to process and display data.

    The process of how to properly pass an Image from a dll directly would more helpful then creating a DIB Data in byte format then saving the bytes to file so as VB6.0 could pick up the image, not to mention other Objects other then the standard types. Arrays are by far clumsy but requiered SAFEARRAYs.

    I am a VB Programmer which was taught both languages but use VB as an interface development tool, then access my oun C++ ActiveX Controls or Simple COM Objects visual studio (7.0 or 6.0)to get the job done.

    More examples are requiered in how to get the OLE ATL objects to more advantage of processing to limit how much we need to access the actual harware and leave that as the last step on the update of information.

  • Anonymous
    December 01, 2005
    Whilst I'm primarily C++/C#, and it is a bonus to have the example in C# (for immediacy of Cut/Paste), I will read examples in any language (VB.NET, J#, Java, assembler :) ) to understand the principals. And the VB-C# code converters do help in getting quick results, that one can later refactor.

    As Tom pointed out, the majority of C#/C++ engineers are more likely to read the examples, regardless of the language.

  • Anonymous
    December 01, 2005
    Whilst I'm primarily C++/C#, and it is a bonus to have the example in C# (for immediacy of Cut/Paste), I will read examples in any language (VB.NET, J#, Java, assembler :) ) to understand the principals. And the VB-C# code converters do help in getting quick results, that one can later refactor.

    As Tom pointed out, the majority of C#/C++ engineers are more likely to read the examples, regardless of the language.

  • Anonymous
    December 04, 2005
    Have the documentation/sample people try the VB samples with VB>C# converter, if the converted code doesn't work ok against test case, then that sample is so complex it should be hand converted to C#.. Most simpler samples should be simple enough for a format preserving conversion. Or have some 3rd party company convert the samples and have them verify the results of it too.

  • Anonymous
    December 04, 2005
    U guys dont want smart programmers but dumb guys who only go the usual way. Putting code in c++ would expose the hidden impl of yr code. U are trying prove VB better over C++, thatz why u even stopped vc++ certification.

    i dont know why u dont want good programmers rather than dumb idiots

  • Anonymous
    December 05, 2005
    Regarding Jeremy's comment about using Java, if we could only say that Java is Java is Java then we might be getting somwhere. VB.Net is VB.Net is VB.Net. The basic question of VB verus C# seems to have something to do with the law of supply (C# developers) versus demand (VB developers)

  • Anonymous
    December 05, 2005
    I use the examples not only to figure out how to do something but to also learn and understand best practices which I assume your examples use. My being able to view and understand examples in VB when I am writing in C#, regardless of how easily it can be translated, does not show me C# best practices.

    I also cut and paste as per the other comments.

    The only reason I will view a VB example is because there is no C# example available. Everytime that happens I swear under my breath at someone in some company and I lose a little bit more of my life force.


  • Anonymous
    December 05, 2005
    I come from a Borland Delphi background. Learning C# is hard enough. But learning C# is harder if samples are in Visual Basic. Not another language (which I won't use anyway).

  • Anonymous
    December 07, 2005
    If it is concidered a true development community, there would be a mechanism for some industrious coder to submit converted examples back to the author and incorporate them. The real issue is time and effort.

  • Anonymous
    December 07, 2005
    Why doesn't MS just finish implementing System.CodeDom.Compiler.CodeParser class that's aleady part of the framework but has not been implemented. It would make this discussion obsolete!

    I don't think it's true that most vb devs don't read articles just because the source is not in vb, I know I don't. I suspect that it's because VB devs are more passionate and vocal about there language because in the past it's been rubished so much, by ignorant people who think that the language you write in determins how good a programmer you are.

    Just finish the CodeDom parser and give VB.NET the ability to write unmanged code and let that will be the end of it.

  • Anonymous
    December 07, 2005
    If I'm looking for copy-and-paste code, any other language than the one I'm using is frustrating, right? I'm mainly into C/C++, so either C# or VB does not help much from that angle.
    If I'm looking for an idea on how to do a job, the example can be in anything I can read (except Perl, of course).

    The main question I have is not "why so many examples in VB", but why the quality of examples, source code etc. has decreased so much? I'm not speaking on the overwhelming aspx.net.vb.ascx.godknows.what samples... but I barely can find something MAPI, for example. In two years probably I'll be asked "what a *** is CoCreateInstance?". And Explorer, IE etc. probably will still use it.

    Remember some (not so many) years ago, when samples were like WinDiff, Process Viewer, Exchange, SQL extended stored procedures ... some of them now defunct, others dying in some obscure WinNT/Sdk/DoesNT/Matter folder on Platform SDK.

    Now I have to browse a N-DVD monstrosity just to find how wonderful I can open an ADO.whatever connection to a database in X ways and Y languages (and most of the time doesnt' work, or when it comes to be really interesting for a beginner, it stops). Thanks, but no, thanks.

    Q: "You have to go to college to be a good programmer?"
    A: "No. You have to read code written by competent programmers."
    (quote from memory)
    Bill Gates said that?

    So where is the competent code? I barely can read a MSDN article today - I almost can't follow the idea, I become bored an uninterested after several phrases. I am the only one? I wonder.

  • Anonymous
    December 07, 2005
    The comment has been removed

  • Anonymous
    December 07, 2005
    I guess Liberalism has reached Microsoft. After the DEMs hand Microsoft there special purpose, they too have become coddlers. VB only programmers are among the most marginal of IT people. I read Mr.Man's comments as saying we should ask Doctors to read and learn from Popup books because otherwise it is too hard for the patients to understand anything. Give Me A Break!

  • Anonymous
    December 07, 2005
    a.c., I think you are saying that you prefer big comprehensive examples, if I understand correctly.

    But I disagree - I like smaller code snippets that just show the topic at hand. If the snippet is in the "right" programming language, then I can copy-and-paste to my test application to try it out directly. I might even start with a snippet and morph that into "my" final code.

    Tom, I think we C# programmers might have to boycott MSDN if there are mostly VB examples.

    Just kidding.

  • Anonymous
    December 08, 2005
    Yyou're right. That IS good Basic (pun intended) business sense; took long enough to figure out! If you're wondering when .NET will take off like VB.x did, it'll be when the VB "Classic" devs commit to VB.NET. And you're right, I don't think they'll be going to C#, or put up with having to read C# ONLY.

    Nice to see VB.NET getting the proper respect it deserves. After all, sounds like that's what's paying the Bill(s).

  • Anonymous
    December 09, 2005
    Im learning vb 6 at the mo, moving on to .net and java next year, the course in my college doesn't seem to be touching c++ or c# and i don't understand why, especially as it has fairly good links with MS. I coded in Vc++ age 14-15 and found it to be a better stronger language. I have not coded in c#, but it has been recommended to me numerous times.
    It now seems like C derivative programmers are being left behind. And if it was the other way round, vb programmers would be in that situation, even if they do make up the majority. In fact, they would be in the situation they were in until the .net framework introduced further OOP elements. (As you can tell, I'm not new to the concepts behind this)

    So a simple solution, which really couldn't be too hard, especially for developers as skilled as those working on this new technology. Print code in both.


    Interestingly enough, to the person who made the point about java, our course next year consists of VB.Net and Java, which i thought was a bit strange :)

  • Anonymous
    December 09, 2005
    After reading all this stuff i understood some things that i'd like to express. Firstly, Mr Archer says that Microsoft decided to provide the public with vb samples, cause from what it seems it's the top of our interestings list. After that, he exactly says, after mr tzagotta's first complains, that : "we are working on 1) Getting authors to submit samples in both VB and C#". It seems to me that something changed here. You firstly say that what you do right now is because of the people interests and that is the right thing to do at the moment and then you seem like to admit your mistake and try to correct it. Am i wrong? i really would like to hear your "final" conclusion on what "you" (meaning microsoft of course) are going to do about it. Finally i want to add that i am a VB programmer and i've never worked on c++ or c# but when something seems to me wrong i must add my opinion on it. After all, i believe that's the purpose of this thread and to be fair the greatest thing you are doing right now is listening to the public's opinion what most other corporations don't do.
    My regards,
    Kdou
    P.S. forgive me for my english. :)

  • Anonymous
    December 10, 2005
    The comment has been removed

  • Anonymous
    December 10, 2005
    I'm generally of the opinion that if I can spend one hour doing something to save a hundred other people ten minutes each, then it's definately worth doing, because that's a saving of over 15 hours overall. In this case it's a matter of the authors spending 1 hour to save thousands of people 1 hour each and really they are just being rude by not doing it.

  • Anonymous
    December 11, 2005
    I'm currently using C#, but I can clearly get your points. I think it's a true fact and a neutral point of view.

    I encountered the same problem with people around me using VB.NET. I don't know, but in my personal opinion, those typical (just like Tom said, not to mention all) VB.NET developers are just too WEAK. With the ease of its specific language features, they're just too stuck with the OVER simplification of those stuffs. As you said, I think VB.NET developers should be accustomed too to the base class libraries as well in order to understand overall meaning of source codes, rather than get stuck to specific VB.NET language construct.

    Though I'm currently using C#, it won't be too hard to read and understand VB.NET (not mentioned VB) source codes. If currently, you have limited resources so that you can only provide sample in a .NET language, I think it's a good decision to provide the sample in VB.NET. And by the time you have more resources later, I think you can (or must :)) provide another sample in C#, C++, and whatever .NET languages Microsoft supports.

    Out of topic, but now (despite whatever language I read), I found that it's hard to understand generic samples, especially those LINQ-related source codes :).

    Cheers people!

  • Anonymous
    December 12, 2005
    If it's such a big deal then one of you convert it and send it back so they can publish it.

    Just need MS to have a place to submit it....


    Schneider

  • Anonymous
    December 12, 2005
    All this debate about what? I have used both VB.net and C#. Personally I use VB.Net. The comment "those typical (just like Tom said, not to mention all) VB.NET developers are just too WEAK" is wrong.

    I can follow C# code as well as VB.NET. I was always taught (especially with programming languages) the minute you know something -something new is out.

    So regardless of what language the "Code Snippet" is in, as a programmer you should be able to follow along and make your necessary changes.

    Or better still figure it out on your own. Then you can write it in the language you prefer.

    How about “Thanks Microsoft for giving us a place where we can go to get examples when we get stuck”

  • Anonymous
    December 12, 2005
    The fact that you are getting complaints from C# developers that are almost identical to those you got from VB.NET developers when there were few examples in VB.NET seems to be a strong indication that you should allocate sufficient resources to produce examples in both C# and VB.NET.

    That will also have the benefit of introducing those that only know one of the two languages to the other language.

  • Anonymous
    December 13, 2005
    This whole debate kills me. Im mostly use VB, but have used C#, and am one of the best DBA's in my company,and btw the lead developer on almost every project I have ever been on. But I guess since I prefer VB im a WEAK programmer, I guess thats why I get paid the big bucks. If anyone wants I'll bring the cheese to go along with the whine.

    For years I heard the same thing out of other VB programmers about all the examples being in C#. pfhttt. Having to read C# code made me a better programmer because I had to understand both languages. I even took C# code translated it into VB and sent it back to the author to post along with the C#. Why, because I could, because it helped me learn. Does it take me longer to understand something in C# than VB, a little, C++ on the other hand is close to greek, but I struggle through to LEARN. Its a lazy programmer who wont read an article because of the language the examples are in. :)

    Quit the stupid language wars, its the Framework stupid. Learn it and when you understand it, the rest will just be duh.

  • Anonymous
    December 13, 2005
    jimmyc, it's not about the language, or the framework, or about being lazy. It's about productivity, stupid. Given your success, I'm sure your time is in great demand, and I would expect you to understand this already.

    We had a software release today, another tomorrow, we're releasing another next week - all different products. We are BUSY. The less time I have to spend decoding a foreign programming language, the more time I can spend getting real work done.

  • Anonymous
    December 14, 2005
    Funny.. I used to be a VB developer, but noticed that there's way more published in C# for 2.0 than for VB... so I learned C#, and there's no going back.

  • Anonymous
    December 14, 2005
    The comment has been removed

  • Anonymous
    December 15, 2005
    The comment has been removed

  • Anonymous
    December 16, 2005
    If you want delete it but send me an email at delsilucas@gmail.com with your answer.

    Hi, i just wanna know if is true that OpenGL it's no longer supported (if it's layered with d3d it's like not supported to me).

    Why you guys do this? i like microsoft (that's the true), and what users will be use the new aeroglass experience? only employees of microsoft.

    Please... take care of OpenGL.

  • Anonymous
    December 18, 2005
    One of the more interoperable languages that compile to the (XML)Extensive Language Markup the Universal Language for Data Exchange!

  • Anonymous
    December 18, 2005
    First it is clear that the readability of Visual Basic syntax incredible over the syntax of Visual C#, which make the VB code more understandable by most developers.

    Second, if you are VB guy or C# guy, all of you is a .NET guys, working with the same BCL (Base Class Library).

    So I think it is right for examples to be in VB as a general trend, and everyone will be able to enjoy the article and code!

  • Anonymous
    December 19, 2005
    "First it is clear that the readability of Visual Basic syntax incredible over the syntax of Visual C#, which make the VB code more understandable by most developers. "

    That is a farce - VB is a pain to read, C# is much much cleaner.

  • Anonymous
    December 19, 2005
    Readability is a function of the reader - what they are used to. A native French speaker would find text in French more readable than a native English speaker. The same is true for programming languages.

  • Anonymous
    December 21, 2005
    What I don't understand is this: Microsoft tells us that there is very little difference in the languages, which being a developer of c++, c#, JAVA, J#, and vb solutions, I believe is true. However, as my hobby, I develop video games in VB.net. If you search the Dec. 2005 DirectX SDK for "*.vb" you will find one file, so needless to say, I am used to converting my samples, but would like to see a fully coded sample, for best implementation, and sometimes copy and paste functionality. As far as most samples, I would just as soon see discriptive pseudocode.

  • Anonymous
    December 22, 2005
    Efficiency in the language of choice is an issue. If there are differences between programming identical code in different languages people would like to know the reasons why. Do you need to perform additional steps in C# or VB ? What is the best or correct way to do something for robustness ?
    This is not an issue of readability but one of poor documentation. If all languages are going to be nearly identical in implementation then there should be polymorphic examples derived from the same source where someone would just request an example in the language of their choice.

  • Anonymous
    December 22, 2005
    I've seen web articles translated by bands of contented readers into Russian, Greek, French...

    Maybe there's an opportunity here. Volunteer translators who rework an article into JScript.NET and all the others.

    In some cases the write-up is going to be different, in others the article can have the control which says look at the code in ... F# ...

    Then you can introduce the the MVT designation for the great translators!!!

  • Anonymous
    December 22, 2005
    It would seem to me that there are numerous language->CodeDom parsers and numerous CodeDom->language converters ...

    Given there are some things which do not fly with the CodeDOM but 99% of the code being discussed does.


  • Anonymous
    December 23, 2005
    The comment has been removed

  • Anonymous
    December 27, 2005
    I think that regardless of the language, "coded" help should be understood by logical content and not by the language specification. Anyway, that's my opinion, thanks.

  • Anonymous
    December 28, 2005
    The one disadvantage I can see with using VB instead of C# is that C# is, in my mind, a little bit more syntactically formal. I am slightly concerned that new code samples will be written with certain of VB's "productivity shortcuts" in mind.

    As long as the article editors encourage explicitness in the sample code, I'm cool with it...

  • Anonymous
    December 28, 2005
    The comment has been removed

  • Anonymous
    December 28, 2005
    Another reason for starting with Visual Basic examples is that VB reads closer to pseudocode or natural language than C#.

    I think that is one reason others are more likely to translate vb to their language of choice.

  • Anonymous
    January 04, 2006
    I'd like to see those numbers. I can tell you that when I search the Internet for .NET code, it is almost always in C#.

    Microsoft.com is really the only place where a find a plethora of VB code.

  • Anonymous
    January 04, 2006
    There is one problem in your statement. In early ears of .net framework, there was most documentation and exams in C#, so I moved from VB6 directly to C#.
    Now you betraying some of your developers which made same switch and which want to see examples in their new language.
    Personally, I don't read examples in vb.net. I like nice and clean code (for example IBS Portal), because I can find some new technique there.
    What I am trying to say is that there aren't only copy&paste beginners. I would like to see examples only to read them, even if they are totally unuseable for me.

  • Anonymous
    January 05, 2006
    who really cares? the point was made that c# developers can understand both languages more easily than vb developers. stop gripping & start writing code so that you can start you own company & do whatever you please.

  • Anonymous
    January 05, 2006
    ben, based on the number of comments to this blog post, I would say a lot of people care.

    I think the take-away point of many of the comments is that MS customers expect MS to provide examples in the primary .NET supported languages. Some folks don't mind looking at other languages, while other folks do mind it.

  • Anonymous
    January 05, 2006
    My favorite examples have the code in vb and c#.

  • Anonymous
    January 05, 2006
    There are several interesting observations here. Firstly, the change in trend MS from showing predominantly C# code to predominantly VB.Net code. I believe that the initial stance from MS was to entice the C/C++/Java community to .Net so C# was the logical choice.

    Now the trends show that the majority of VB6 programmers have stayed put and not migrated to VB.Net. Add to that the years of complaints about the lack of VB.Net samples and MS finds that it's in their best interests to encourage these guys to ".Net land". Hence, the change to VB.Net samples. Although, I believe the resistance to moving to .Net is mostly because of legacy apps having to be maintained rather than the availability of VB.Net code samples.

    The second point is that MS already do code swapping on their sister site www.gotdotnet.com where you can check out/copy/paste the solutions in VB, C#, J# and C++ by the click of a button. NB. User provided solutions, however, are not editted by MS and so appear in the language of choice for the developer.

  • Anonymous
    January 05, 2006
    The comment has been removed

  • Anonymous
    January 05, 2006
    If you have #develop, there is a conversion utility built into it that allows you to quickly convert from one language to another. Youc an use this to quickly copy and paste the vb.nET example to C#. I highly suggest it. However it boggles my mind that MSDN can't do the same thing automatically, its easy to convert VB.NET to C# but occasionally you get some issues on indexors. Pick up a copy of #develop. Its great and the conversion tool is worthwhile. If MS made their samples in C# it woudl be easier to convert internally to VB.NET than the other way around. Also, they want to retain their VB.NET sheep but this also makes Java, Python etc developers less apt to try to convert it to C# as well. They are missing out on NEW developers to .NET the more they focus on VB.NET.

  • Anonymous
    January 05, 2006
    The comment has been removed

  • Anonymous
    January 05, 2006
    Sorry for the late comment, just ran across this.

    Code examples should be in at least three languages - C#, C++, and VB.Net - if not more (e.g. JScript.Net, J#, IronPython). It's a matter of spending the money or not, and it should be spent.

    Documentation is key to an educated developer base, and deserves the resources it requires to do it well and completely. Any argument not to do so is a cop-out.

  • Anonymous
    January 05, 2006
    As a C, C++ programmer/lecturer I understand completely that Visual Basic has much broader support. It's just easier to get along with..and it's where Bill and Microsoft really started with Microcomputers, not DOS and PCs as popularly believed by the media hypos.

  • Anonymous
    January 05, 2006
    While I can say I fully understand the reasons behind the decision to produce the majority of tutorials in VB.NET, it also sounds like that means "only" a VB.NET example.

    I'm not afriad of converting between languages, as most are fundamentally the same. As a long time programmer of 18 years, having started out in Pascal, and progressing through C++ and now C#, I do have issues with VB as a language in general. As a result, I avoid it like the plauge, and avoid including any developers on my team who only have experience with VB.

    Granted, VB is what made Microsoft what it is. As a large developer base is key to an operating systems success, VB was a wise business move. But I think I'm correct in understanding that this move to VB tutorials means the situations where a guy like myself would need an example, will also be the situations that now have VB rather than C# examples. I can't stand reading VB, even just to get the gyst of something, which now pretty much kills off my primary source of example code.

    My hope is that for significant articles that present significant or complex examples, you'll put in the effort to produce both VB.NET and C# examples.

  • Anonymous
    January 06, 2006
    The comment of 3:1 VB to C# is that 2 of 3 VBers are still using VB6.

  • Anonymous
    January 06, 2006
    The comment has been removed

  • Anonymous
    January 06, 2006
    VB programer are just more dummy!! ;o)

  • Anonymous
    January 06, 2006
    Hi tomarcher.. I am not suppose agree your point.

    Really I hate to programm in VB.NET, and love to do it with C#..

    Where is the Language Chooser Tab ...

    Basically converting the code from C# to VB is simple and easy but from VB.NET C# bit complicated..

    We need to track all the variable declartion to find weather the statement is array or function and etc...

  • Anonymous
    January 06, 2006
    Save a Tree - Drop vb!!!

    AddHandler/AddressOf, Inherits/Implements, Must Inherit/Not Inhertible, Dim, (Hijacked) As. . . and the notorious "shared" (someone please explain that to me!)

    What the %$%# is all that???

    VB promotes poor programming practice!
    The language is backwards.

    Force the VBers to learn C# . . . It will do them good! And maybe my workload might lighten up!

  • Anonymous
    January 07, 2006
    Who can dispute the mastery of web development demands a mastery of client-side development as well as server-side development?

    Nobody.

    Who can dispute that client-side web development does not require a mastery of the legacy C syntax and grammar?

    Nobody.

    Thus, all code snippets for web development should be in C# because the syntax and grammar of C# coincides with that of client-side script. No need to fork the cognitive well-being of the web developer when reading code published as a sample.

    All code snippets for Windows Applications should be in VB.NET. No need to fork the cognitive well-being of the Windows application developer when reading code published as a sample.

    Publish web development code samples in C#.

    Publish Windows application code samples in VB.NET.

    This is a logical solution to the forked Microsoft programming language dilemma.

  • Anonymous
    January 08, 2006
    The comment has been removed

  • Anonymous
    January 09, 2006
    What seems to be going on here is that VS2005 has attracted a lot of Php and Java coders who are now using the tool. So they need the samples.
    I have long been complaining that MS is devoting way TOO MUCH of the samples to C#. From what I see, there are more C# samples than VB. I complained about this http://weblogs.asp.net/scottgu/archive/2006/01/07/434787.aspx#FeedBack for the second time.
    Thanks for taking a stand.

  • Anonymous
    January 09, 2006
    Here is a MSDN Magazine article describing an add-in that automatically converts C# code to VB:

    http://msdn.microsoft.com/msdnmag/issues/06/02/PasteAs/default.aspx

  • Anonymous
    January 09, 2006
    The comment has been removed

  • Anonymous
    January 10, 2006
    why is MS risking angering/alienating any group(C#,VB, C++) by limiting to just 1 and telling the rest to figure it out?

    I don't belive its VB programmers who are lazy, it seems to be Microsoft!


  • Anonymous
    January 14, 2006
    Firstly I would imagine Mr Archers problem to be time, writing and testing examples in 3 languages takes 3 times as long, do you want a vastly improved product 3 years late just so you can have your hand held throughout the learning process?

    As well as this the internet is awash with excellent non-MS help, sites devoted solely to C++, C#, VB .Net all with blogs/forums and MS most likely know this.

    I always wonder if, like me, most programmers find the main problem is not syntax but library knowledge, especially in something as large as the FCL, therefore I appreciate what help is available in any programming language.

    I think too much emphasis has been placed on language syntax here, the .Net FCL is consistent across C#, VB.Net, C++ .Net and the first 2 are almost syntactically identical; its much easier for people to pick up all 3 languages as opposed to developing in VB 6 and trying to use examples in MFC or vice versa.

    What do I want? stable operating systems, better database management, and cheaper licencing. Can we have some of that please?

  • Anonymous
    January 15, 2006
    The comment has been removed

  • Anonymous
    January 16, 2006
    to start off it is annoying that there are more code exampples in VB than in C#, but over the years of programming C# i have been able to understand most of the examples written in VB and implement then.

  • Anonymous
    January 17, 2006
    Thanks for all the examples. Whatever language they are in!

  • Anonymous
    January 17, 2006
    Thanks for all the examples. Whatever language they are in!

  • Anonymous
    January 17, 2006
    The comment has been removed

  • Anonymous
    January 17, 2006
    The comment has been removed

  • Anonymous
    January 19, 2006
    The comment has been removed

  • Anonymous
    January 19, 2006
    There are some sites that offer software to convert the source code from one language to another.

    Surely Microsoft has the resources to make such a translator to translate examples from one language to another.

    Why not build it?

  • Anonymous
    January 19, 2006
    Why not just support them all without actually doing it yourself - follow the example of a site like wikipedia and allow viewers to post it, if you look at open source sites on the net people will often post conversions up after they are done, just make it simple enough to do and it won't matter too much what language you put it in because for anything good it will be translated within a few weeks.

  • Anonymous
    January 19, 2006
    I'm a C++/C# programmer and if I see an article with only VB examples, I skip it - not worth the hassle to do the mental translation.

  • Anonymous
    January 19, 2006
    Providing less samples in C# is a disappointment, regardless of anything else Microsoft does. Moreover, since I (and not only me) do not have Visual Studio but only C# Standard I would say it would be sane to include both C# and VB.NET in each and every single product shipping with the VS IDE. That way at least we can compile those friggin VB.NET samples and maybe even use them.
    This will also show Microsofts' commitment to VB and C# as first grade languages for .NET.

    As to the '3:1' argument mentioned, did you also investigate how serious those VB developers are? Isn't it so most casual developers will use it even after being warned twice? I agree with most arguments against this argument mentioned in this thread.

    Maybe you should rename VB/VBA to be Verbose Boundless (Antonym). That will maybe make sure new programmers will think twice before they pickup on it. And yes, C# is easier IMHO, regardless of my preference.

    Now on MSDN::: (20 jan 2005)
    http://msdn.microsoft.com/vbasic
    Paste As Visual Basic: A Visual Studio Add-In That Converts C# Code To Visual Basic
    http://msdn.microsoft.com/vbasic/default.aspx?pull=/msdnmag/issues/06/02/PasteAs/default.aspx

    Hmm, I guess this can be done the other way round then, too, isn't it?

  • Anonymous
    January 21, 2006
    Something I learned from my college professors...how to be a programmer.

    Something to learn from the humble...what is the meaning?

    Something I learned from the wise...to use the right tool for the job.

    A true developer needs only algorithms and reference, not syntax.

  • Anonymous
    January 21, 2006
    Something I learned from my boss...how to work quickly and efficiently.

    The point is not whether I have the ability to convert VB examples to C#; it is whether I have the time and whether that is the best use of my time.

    A true developer is concerned with total effectiveness, not with busy-work like converting example programs from one language to another in order to understand a programming concept or API. This should be done already in the documentation.

  • Anonymous
    January 22, 2006
    The comment has been removed

  • Anonymous
    January 23, 2006
    We all know what the end result of seeing many VB articles will be...VB developers, if they don't climb the learning curve will always remain lousy VB programmers, please no offense, this is what the article surmised.

  • Anonymous
    January 23, 2006
    You could always allow the community to solve the problem for you by placing a link on each article that has examples only in VB.NET. The link would allow a community member to login and provide equivalent example text in C#/C++. Once the code was reviewed by 5 members or 1 employee it would become the standard example text for that article.

  • Anonymous
    January 23, 2006
    All I can say is that VB coders don't know how to program. You even basically argued it yourself since C# and C++ people can convert VB into thier respective languages. I think this a real pity though. If MS wants the quality of applications to increase then why not make people learn a better programming language rather than catering for all the people which are still using a language which is way past it's used by date. All MS is doing now is annoying people who have taken the time and effort to try and write better programs with a better language and probably making them wonder why they didn't stay with VB. There's a difference between just giving the consumer what they want and empowering them to want and use something better.

  • Anonymous
    January 24, 2006
    Could we move the dicussion to something more positive, rather than going around in circles?

    It does seem that the impetus behind the original decision is to move VB programmers from VB6 to using .Net. I made this transition when working on a very large enterprise project during the beta phase. I found that (at the time) most of the information available was in C#. So, after reading books with code examples in C# and having no problem at all with the syntax of curly brackets and colons, I transitioned to C#.

    It was easy to move to the new language, and the reason I did so was to take advantage of what the .Net framework could do.

    Because of this, if we want to encourage VB6 people to move to .Net, shouldn't we be accentuating what the .Net can do over COM?

    A very clear advantage is the difference in security. Have a look at:

    http://www.charteris.com/publications/whitepapers/default.asp

    The paper:

    Security Solutions Offered by Visual Studio .Net 2005 (Whidbey)

    demonstrates how far applications can move forward from a security perspective both within each application and within the enterprise.

    Wouldn't more of this encourage the transition? I think this is what is required, rather than making allowances for familiarisation of syntax (ie. letting VB6 people know they can still use the Dim statement).


  • Anonymous
    January 24, 2006
    This thread is an embarsement to microsoft developers.

    Funny how Microsoft promotes C# as the language of choice for .NET but then caters everything to VB programmers.

    Most contracters I see that use VB also have very poor software design skills.

  • Anonymous
    January 25, 2006
    Although I program in all of those languages in my contracting work, I find that most employees I see that try to use C# have dreadfully appalling software design skills.

  • Anonymous
    January 25, 2006
    Let's face it folks...VB is sloppy, sloppy, sloppy. VB promotes extremely poor development practice. BASIC was great for what it was intended to do originally: teach the basics f machine language and organization. Unforunately, through Microsft's insistence, it has morphed into a sloppy, dreadful Frankenstein of a language.

    I started as a Pascal programmer. Now that was a well organized, thoughtful language for teaching more advanced, higher-level programming principals. I migrated to C in my professional career, then C++ and now C#. I simply will not buy books written by Visual Basic developers, nor will I read articles where examples are written only in VB. I have found such books and articles generally to be sloppy, poorly written or of the "follow these steps exactly" type. I don't want exact steps to follow to achieve a result, I want the theory general overview of how to solve a particular problem. Unfortunately, MOST VB programmers don't want to do the EXTREMELY important task of actually understanding what it is that a particular piece of code is doing - they just want cut and paste examples. Sloppy, sloppy, sloppy. Not to mention horribly ineffecient.

  • Anonymous
    January 27, 2006
    Now that you mention you it... Either your spelling or your typing is sloppy:

    Check these out:
    Unforunately -> Unfortunately
    Microsft's -> Microsoft's
    principals -> principles
    ineffecient -> Inefficient

    How about grabbing a spelling book instead on your next trip to the bookstore. This makes me wonder if your code is just as sloppy... and stop dissin' VB.NET programmers until you can spell right.

  • Anonymous
    January 28, 2006
    This is unfortunate. Four points to make:

    1. C# is the de facto .NET language, and not having MSDN examples in it is broadly ridiculous.

    2. For the purposes of demonstration, the differences between code written in the core .NET languages are mostly syntactical and usually trivial.

    3. Even if the reader can translate himself, it is likely to be a bad use of his time.

    4. The idea of community translation has recurred throughout these comments. What a fantastic idea for Microsoft - you could build a whole community of translators with some kind of self-correcting/validating mechanism. A cross between wikipedia and experts-exchange... Think of the developer loyalty it would breed. There could be Microsoft certifications to be earned!

  • Anonymous
    January 28, 2006
    The comment has been removed

  • Anonymous
    February 01, 2006
    It amazes me that people seem to think that "because you use VB you are a bad programmer." Get real people! What makes a person a bad programmer is their knowledge (or lack thereof) in software design. I know plenty of C# programmers that are bad programmers. Same is true for VB programmers, C++, Java, Delphi, Cobol, Pascal, etc., etc.

    Good programmers know how to -
    *perform a good thorough analysis of the project
    *turn the results of the analysis into an object model
    *use efficient coding techniques and patterns
    *separate presentation logic from business logic
    *modularize your code
    *use good coding standards and naming conventions
    *etc, etc.

    And all this can be done (or not done) irregardless of what language you are using. The problem with bad programmers is that they do none of the above points. We have schools churning out programmers who have only been taught the "language" and not "software design". Look at the majority of the books being released. Every book out there will tell you, "2005 has generics this is how you code it.". No one is saying "this is generics, use generics when you need to....don't use generics when you need to ....when using generics always do.....never do....". We need more "best practices and guidelines" books than we do "how to" books. We could get rid of VB altogether and guess what, we would still have bad programmers. As long as this "how to" trend continues you can expect bad programmers to be around for a while. If your focus is "I use this language so I'm a good programmer", then IMHO, you are probably a bad programmer, LOL!

  • Anonymous
    February 03, 2006
    VB is more prominent simply because it's easier to train in initially and is therefore being taught in a more widespread manner than C#, at least in my experience (undergraduate CIS student), and at an earlier stage in a software developer's training. Perhaps training in C# would be easier if Microsoft focused more on C# than on VB. Overall, there would be an increase in C# coders and less VB coders. There would also probably be less coders between the two; but, the average quality of software developed will likely increase because fewer undedicated, sloppy programmers would be tempted to get into coding.

    I mean, just the idea of programming in VB is less intimidating than programming in C#, so potentially sloppy VB coders will lose interest if the number of clients who request C# coding increases. I'm not saying VB coders are sloppy. I'm saying that, because VB is easier to comprehend than C#, more amateurs will develop using VB than C#.

    I'm talking about actual coding, not slapping a bunch of text and picture boxes together and calling it a program. In that case, VB and C# are about equal to each other. Also, code is only as sloppy as a coder makes it. However, there are more opportunities for lazy programming in VB than in C#.

    By having Microsoft promote professional programming practices more than just producing applications quickly, more consumers will be pleased with their applications and will operate more efficiently using them. This will hopefully lead to better business in IT and, potentially, a much more smoothly-running economy. It's the quality over quantity argument.

  • Anonymous
    February 04, 2006
    I definitely prefer C# over VB.NET, except for the VB.NET webcasts I presented , where it would have been awkward to have used C#. I generally use C#, I can express my examples better, there's less chance of error, and you're much more likely to get the content in a timely manner ;)

    The one issue I would raise is that there are language features in C# that do not map easily to VB, and I see many dual-code examples where the C# code is simply a lieral translation of the VB. I've seen many C# examples that didn't employ the using(...){} syntax -- apparently because it didn't match the adjacent VB code (or maybe the author was more familiar with VB). I would definitely prefer that examples in any language leverage the language rather than being presented in some weird common subset. Frankly, I'd be happy with examples in F# if it illustrated a better approach to solving the problem at hand.

    And I'd definitely like to see some Eiffel examples.

  • Anonymous
    February 04, 2006
    Tom Archer posts about MSDN preferring (or not) one language over another (link from Brian Loesgen):http://blogs.msdn.com/tomarcher/archive/2005/11/21/495282.aspx...

  • Anonymous
    February 06, 2006
    While I believe the sheer number of VB programmers may in fact be greater (though that number may be skewed - since I would bet more C# programmers know VB than VB programmers know C#), my gut says that the whole story isn't being told.

    What is the statistical make-up of the readers of the article? - It seems that a large number of VB programmers wear a couple of hats, thus having limited time to spend reading general programming articles, whereas C# programmers seem to be mostly Programmers and seem to treat their profession as a science to be studied.

    Then based on the number of article readers - what is the break down (percentage-wise) of readers actually copying and pasting code (or downloading) in one language or another?

    There are a host of additional questions - but the point being - just because there are statisically more people that know a particular language doesn't mean you have gained the statistical advantage by catering to that language. There are host of questions around audience, sociological interactions, user perceptions, user response, value percieved/gained by the audience - and MS should tread carefully focusing on a particular audience based on world numbers.

  • Anonymous
    February 07, 2006
    Some seem to be arguing that VB encourages sloppy programming because the user-friendly nature of the language encourages amateurs to take up programming. The more non-professionals programming in a language, the more "sloppy programming" will exist in that language. Is user-friendliness a defect in VB? I would say it's a strength.

    Don't be afraid of the amateurs; they are not a threat, they have a right to exist, and their inferior programming makes yours look better, which is a good thing, isn't it? I for one applaud Microsoft for bringing power to the people.

    I'm sick of seeing this racist argument "VB is inferior because look at the people who use it". No, silly, look at the language. And the language is neither superior nor inferior to C#; it's just more wordy, which some people prefer (if they can touch-type).

    Which language is easier to be understood, not in an absolute sense but by users of the other language?  I would guess that VB's verboseness is less of a problem for C# people to read than C#'s lack of wording is a problem for VB people to read. Conclusion: although providing the code in both languages is best, if it must be one or the other, choose VB.NET.

  • Anonymous
    February 08, 2006
    The comment has been removed

  • Anonymous
    February 08, 2006
    if you want vb to C# for you to copy and paste just use reflector...that's what I do..hehehehe

  • Anonymous
    February 11, 2006
    Windows Stinks, Use Linux.

  • Anonymous
    February 12, 2006
    It does not matter what language it is, if you are a programmer working on the Microsoft platform you should have a good understanding of VB, C# and C++. I prefer C#, but it is not that hard to read VB or C++. Honestly, if you can’t understand the syntax and you are too lazy to work it out, maybe it’s time to go back to your old job at KFC or change industry.

  • Anonymous
    February 13, 2006
    I demand that all examples be written in Assembler.NET.  

    Also, I am Dutch.  I want all of the program code comments written in broken English so that they are more easy for me to understand.

    Very much thank you.

  • Anonymous
    February 15, 2006
    C++ programmers have a choice between a wide variety of compilers and development environments.

    C# programmers have at least the option of switching to Borland or Mono.

    But people who choose to program in VB are pretty much stuck with a single vendor.

    So isn't that a good enough reason for MS to encourage VB?



  • Anonymous
    February 16, 2006
    i think it's because there Visual Basic.net Programming is getting more powerful by the minute. Think about it. when VB 6 came out it was at an ok speed, while compiling. but  Vb.net is easier to understand say than C++ or C# but it was not as powerful. now its getting more powerful and is getting eaiser to understand. i use to do most of my programming in VB.net but know i do it in C# because C# is simular. so i learn't but i think C++ is history know i think Vb is the future.

  • Anonymous
    February 16, 2006
    I really like the community contribution idea is a winner. There seems to be enough passionate people out there to take part in writing translations for code samples.

    Here's a quick view of the benefits:
    1. Microsoft gets to keep VB first policy and can churn out more articles quicker.
    2. The usual 15 minutes of fame for the really passionate writers and enthusiasts.
    3. Peer review would preserve the quality of all the conversions.
    4. Nearly 100% audience coverage (i.e. many languages)
    5. .NET Development gets a tremendous boost by having the most accessible code samples - unrivalled compared with any other platform on the planet, wins by sheer mass of volume (and quality).

    Adding a small financial incentive for successful and accurate contributions wouldn't be all that difficult, and would further drive participation and promote best practices.

    Microsoft is fantastic for bringing technology to the common man, so finding the sweet-spot-multipliers is a good thing. Imagine being able to search for a 'how-to' and find a perfect example and article, in the language you prefer, every time?

    Go, you good thing.

  • Anonymous
    February 16, 2006
    Thanks for mentioning about many examples in Visual Basic.  I frequently looked for help via Internet (Microsoft) and it mostly gave an example based on Visual Basic.

    I have no question about it because it is very understandable that Bill Gates wanted this! I believe that is favorite computer language and he had a right to tell Microsoft to write examples in Visual Basic.

    About me, I currently write code in C# and Java. I used to use VB 6.0 for 2 years and it was a good language, but I believe it has a lack of object-oriented programming as C# or Java.

  • Anonymous
    February 16, 2006
    Just a quick point:

    doesnt matter what language its in really, we are just looking for a "How do we do this" most of the time anyway... Its the gist of the article, not the exact syntax, that matters. If you dont know the language well enough to work out the exact syntax in ten minutes, you arent going to understand the sample anyway :) We really just need to know that this sample does this and this is the namespace that deals with it.

    And out of curiousity, why do people say that c# is the basis of .NET? I though MS released it all at once... having used both, its really only the readability and syntax that change??

  • Anonymous
    February 18, 2006
    The comment has been removed

  • Anonymous
    February 19, 2006
    Its ok, I love both VB and C#, and I love converting VB samples to C#, but there should be some hints for C# and developers for other languages.

  • Anonymous
    February 20, 2006
    More VB developers than C++ or C#...... maybe, but are these VB developers creating anything useful, I doubt it (I've never seen anything writing in VB that isn't smoked by an algorithm written in another language like oh I don't know C perhaps......)

    I don't use VB or C# because I want something that's close to the language everyone uses and that language is called "C".  C++ code is mixed with C on a daily basis and to tell me that there are more VB developers than C++ makes me laugh because every USEFUL developer I know sticks to C.  If they stick to C that means when they go outside of the realms of C they use C++ (I know this, you know this, this topic makes no sense at all!)

    I too agree that MSDN does not have enought C++ examples (I don't care about C++ since I use C, but VB or C# is completely useless to me and I'm 100% sure I'm the majority here)

  • Anonymous
    February 21, 2006
    By limiting the examples to VB you limit the future growth of programmers to only VB.  As a result you will continue to have a large number of VB programmers over C++.  Doing this only increases that gap.  

    As someone who has a desire to move toward C++ without code examples I ultimately will be lost at times because I wouldnt know where to begin with code conversion.  Granted most syntax can be easily recognized and converted but many  methods are not done easily by the entry level developer.  There would definately be a decrease in clean code development without examples by those who are forced to convert code in thier own creative and most inefficient ways as opposed to seeing how a professional coder would write a specific routine.  

    I would also say the number one reason for me not learning C++ is the current lack of good training materials and examples.  I prefer visual training first then book training to reinforce my understanding with code examples.  This really limits the learning potential for aspiring developers.

  • Anonymous
    February 21, 2006
    "Real" developers don't need any documentation.

  • Anonymous
    February 21, 2006
    Lets face it, VB programmers need their hands held a lot more than any other programmers - so lets let the baby programmers have their time with mummy.

    P.S. And to Kolg - I'd be happy to use Linux if it didn't have some many bugs in it. Maybe MS can bring out a GUI less, royalty-free version of Windows for remote servers and single tasking embedded devices.

  • Anonymous
    February 22, 2006
    Probably if you show C# code, the VB programmers would convert to C#. We all know that C# is a better language and it's probably time that VB programmers make the step to C#.

  • Anonymous
    February 22, 2006
    Saying C# is better than VB, is like saying that the French language is better than the German language. In other words, it is illogical.

    To a C# programmer, C# is a better language.

    To a VB programmer, VB is a better language.

    There are probably very few programmers choosing to work in a language that they do not consider to be the "best."

  • Anonymous
    February 22, 2006
    What about gamers versus business programmers?
    What about web programming versus desktop?
    What about library programmers versus ClientServer versus Ntier, remoting, and dcom programmers?

    Do you think I am not a worthy contemporary? Can you guess which languages I write in? Can I work for non fortune 100 companies and still be respectable.

    How are you with requirements, collaboration, class, and sequence diagrams? Have you read CodeComplete, PeopleWare, and the Mythical Man Month?

    Are you studying the history of your craft so as to not make the mistakes of your predecessors?

    I have done all of that, am self taught, not certified, and never taken a compsci class in my life.  Now can you guess???

    Either language is fine, as long as you don't already know one and switch to the other to become someone else. Learn the other language to be better in the one you love.

    If you don't love what you do you are in the wrong business.  This stuff is hard and it not getting any easier.

  • Anonymous
    February 22, 2006
    I really can't put up with this anymore.  I think I'll just retire.  

  • Anonymous
    February 24, 2006
    My Name İs Hakan

  • Anonymous
    February 26, 2006
    Why don't Microsoft just invent, or re-invent and pretend they invented, another language that's new to everyone and use that for their samples, then nobody (or everybody) can complain.

    On a serious note, why not just present samples that are not dependent on any particular language feature in a general pseudo code, understandable by everyone.

    I'm thinking mainly of the samples given for how to use the .NET framework and similar code.

  • Anonymous
    February 27, 2006
    Why so many questions about the examples being in VB.NET
    Live with it :-) !!!

  • Anonymous
    February 27, 2006
    The comment has been removed

  • Anonymous
    February 27, 2006
    Andy MC,

    You are talking about the number of 'vacancies' not coders.

    One could argue that your example proves the point that there are more coders in VB than C# and thus that the VB vacancies are filled already!

  • Anonymous
    February 27, 2006
    Dr_Sam,

    I agree with much of your post except two points:

    "Who cares if developers write what appears to be "sloppy" code that you cannot easily understand!  If it works, it works!  And if development is done in a quicker and easier manner, with less learning effort and less debugging time, isn't that a smarter way to develop?"

    If you've been programming for 23 years I can't understand how you can ask that question. Have you never been asked to maintain (or build on top of) someone else's code? The initial release of ANY code is not the end of the story as you well know -- sloppy code, whether it initially works or not, will almost always result in more headaches, costs, and delays when more than one developer is asked to deal with it.

    The other statement was that Managed DirectX runs at 95-98% the speed of its unmanaged counterpart. I suppose for some apps that's negligible, but for any serious gamer or game developer, it's not an acceptable compromise. Not to mention the fact that even the smallest MDX apps have the added dependency of the .NET framework.

    Cheers,
    Darren

  • Anonymous
    February 27, 2006
    I love this debate and the fact that it has been raging on with these comments shows I'm not the only one...

    I'm not here to take sides, though I have my own side, I'm here to ask where tomarcher went...  He bowed out rather ungracefully in my opinion back in November, namely the same day he posted the article.  

    If he ever chooses to comment on this matter again (because I know he's still reading), I just have one question ... does Microsoft have a plan to remedy this problem, or do they not even see it as a problem?

    tomarcher.... come back!

  • Anonymous
    February 27, 2006
    Interesting question !!. Microsoft is showing that not everything easy as we think. MS is just giving us an idea behind any system. We should uderstand it and keep using examples in VB.NET to develop C#.NET application

  • Anonymous
    February 28, 2006
    Well I might be prejudiced but I have never ever consindered any code written in VB as anything worthwhile reading. So I simply skip anything in VB.

    I am mostly programming  in C++ and when some project really really needs it in Java or C#.  

    But knowing the true power C++ can give you, I find VB way too simplistic and insufficient.

  • Anonymous
    February 28, 2006
    While readin through the entire section, I find no matter what language u use, as long as you are able to get the job done in the fastest time.

    In other words , VB.NET Rocks !!!

    And referring to the last comment, who says VB is insufficient, who gave the world GUI Programming, was it C,C++ or C#, it was VB first, dont forget the root, as to where MS is today , thanks to VB :).

    VB.NET , go get em :).!!!

    VB.NET SUPPORTER

  • Anonymous
    March 01, 2006
    Just use a VB.Net to C# Convertor...It's simple.

    I program in VB.Net and if i find a code sample in C/C++ i convert it using on eof the many convertors that there are scattered around the internet.

  • Anonymous
    March 01, 2006
    I feel that even after Microsoft releasing the .NET platform, people think that VB.NET is not so powerful because of their understanding of VB 6 or below.

    As a result many non VB programmers ignorantly say that VB is not powerfull. It is my suggestion that they remove this mind set for Vb.NET because Vb.NET is now just as powerful and the number of developers are increasing for Vb.NET.

    I am very happy to see a lot more codes in VB.NET.  I can easily convert from VB.NET to C# if I need to.

  • Anonymous
    March 01, 2006
    Let's just dump VB and be done with it. The quarter of the vb crowd that has more than one brain cell will be able to adapt to a real language and the rest can get a nice job at mac D

  • Anonymous
    March 01, 2006
    Hey whogivesa, you need help but we understand.  

    By the way, who is "Lets". Are you running anything??? Get back to work before some offshore company takes your job.

    Isn't it cool how the offshore crowd dispises vb as much as you do and write bad C code that local vb developers get to rewrite when employers learn what RAD really is????

    See you at MacD. Just don't burn my burger like you do your bridges.

  • Anonymous
    March 01, 2006
    does anyone know how to do IsNumeric, IsDate, and use  a WITH statement in C#?

    i am trying to convert some IsNaN in javascript classic asp to c# and I think I need VB.

    if C# is not capable of this I will use VB.NET because I know that works.

    thanks in advance. I don't care which language, I have lots of time I think C# because people say it is easy to learn. I am a javascript programmer

  • Anonymous
    March 01, 2006
    C# does not have WITH, ISNUMERIC, or ISDATE.

    you can use any .Net language just set reference and using directive to point to Microsoft.VisualBasic.Information

    or your alternatives are regex, try-catch on int.parse(value), int.TryParse, or char loop to test each ascii in number range, etc

    hope that helps.

  • Anonymous
    March 02, 2006
    What makes this whole discussion a moot? point is the fact that VB has evolved from a VB (BASIC) development environment to one that allows one to use different language segments with in the overall code.
    ie (VB.Net; Java, J#,C#,VB,C++,inline code,etc...)

    Discussion as to which one is 'best' are just futile exercises as in which 'religion' is best.
    Each one has its good points and bad points. Just utilize the one you know best and 'please' try to use other examples (as in VBers trying C#) to enhance your 'worth' to employers. I have in my past as a VBer had to also write scripts for PROCOMM as that was what was needed at the time. Be versatile...

    JMHONM

    Thankx
    CBWoodSr

  • Anonymous
    March 02, 2006
    According to Bruce Lee:

    I fear not the man who has practiced 10,000 kicks once, but I fear the man who has practiced one kick 10,000 times.

  • Anonymous
    March 02, 2006
    The comment has been removed

  • Anonymous
    March 02, 2006
    Your article seems for me in the same category as where once in Calfornia was statical proven that kids come from cabbage.  (A large investigation on a minor school had proven that).

    I am active in C# and in VB.Net newsgroups. My expirience is that VB.Net developpers can more easy read C# samples than visa versa.

    Don't forget that VB.Net is more extended than C# and can therefore be less easy to read for C# developpers. The same reason as that it is easier to convert C# to VB.Net than visa versa.

    What I hate are those direct from C# with a tool converted samples on MSDN showed as VBNet however wich miss all points of VB.Net. Because of what I wrote above you see those often. Converting real VB.Net to C# is much more work. Maybe is that the real reason.

  • Anonymous
    March 02, 2006
    You can't call your self a programmer is you use Visual Basic.
    Any "language" that doesn't have pointers isn't a language.
    C++ is the most efficient and most powerful of the 3 languages discussed in this forum, so why not lean it. If you are not smart enough to learn C++, DONT PROGRAM COMPUTERS. Infact, you might need to get a breathing machine because you are so stupid and might forget to breath on your own.

  • Anonymous
    March 03, 2006
    sub {
    VB loves C#
    End Sub }

  • Anonymous
    March 03, 2006
    @David:

    How could someone get so stupid and misguided? 1 Pointers are not that useful (useful but only in certain situations). 2 VB has an alternative, Peek Poke Varptr Varseg etc.

    @the topic:

    I think this is good. I am a BASIC programmer at heart, recently began VBing and am very glad that examples will be in VB. VB code can be easily converted, whereas C/++ can often get very messy and tangled up. You should also give in Java as there are so many programmers of it.

  • Anonymous
    March 03, 2006
    @David,

    Please don't try to be arrogant. I hate arrogant people.

  • Anonymous
    March 03, 2006
    thanks to providing free materials. but i couldn't open that free materials.how can i that free materials? please send me these material site or url links

  • Anonymous
    March 03, 2006
    thanks to providing free materials. but i couldn't open that free materials.how can i that free materials? please send me these material site or url links.

  • Anonymous
    March 03, 2006
    i wnat to access free materilas from this site. how can i do it ?

  • Anonymous
    March 04, 2006
    The comment has been removed

  • Anonymous
    March 05, 2006
    The comment has been removed

  • Anonymous
    March 06, 2006
    The comment has been removed

  • Anonymous
    March 06, 2006
    Asdrubal Chirinos nobody cares what you have time for. Your value to the programming community is nothing.

    if you want to continue calling vb coders baby and foolishly believe C# will dominate you are sadly mistaken.

    and your point about not supporting the 80% you think don't have a clue is counter intuitive. I think what you meant to say is you are clueless and need the examples in C# because your too scared you will not be able to keep a job without the examples.

  • Anonymous
    March 06, 2006
    Yes I am sorry to have offended anyone.

    ASD

  • Anonymous
    March 07, 2006
    The comment has been removed

  • Anonymous
    March 07, 2006
    The comment has been removed

  • Anonymous
    March 07, 2006
    The comment has been removed

  • Anonymous
    March 08, 2006
    C# is part of the new .Net environment. That's all fine and dandy for those who want to go use a new language, but let's remember that VB is the long-time anchor and therefore should be the focus of all examples. Whe we needed a new language is beyond me anyway, since .Net was originally VB7! VB should be the flagship language for examples due to the customer base.

    having said all that, there is one easy solution. Microsoft has a bzillion employees doing everything imaginable. Why on earth are they not providing BOTH versions of code examples in everything the put out? Seems like an easy solution.

  • Anonymous
    March 09, 2006
    The comment has been removed

  • Anonymous
    March 09, 2006
    Mark, you have missed the point of C#. C# gives you a good language syntax (best of C/C++/Java), good performance, and rapid development. It is the best of both worlds.

    VB and C# are not redundant. C# is necessary because many past C/C++/Java programmers will NOT use VB. But we still want the benefits of VB.

    Since switching from C++ to C# (we were VERY hard-core C++ users), we've seen productivity improvements and also small application performance improvements relative to C++. So we're happy with it.

  • Anonymous
    March 09, 2006
    hi tzagotta,

    perhaps i have missed the point.

    you said C# gives developers good performance and rapid development, and it's the best of both worlds. you make a strong argument for using C#, but since vb's main goal is RAD, and now you have C# which provides that and offers better performance, to me that says vb, was in fact, made redundant.

  • Anonymous
    March 09, 2006
    Mark, VB is valuable to developers already proficient in VB.

    To summarize, C# was developed to attract C/C++/Java programmers to .NET, and VB is carried forward for the millions of active VB programmers.

  • Anonymous
    March 09, 2006
    The comment has been removed

  • Anonymous
    March 09, 2006
    The comment has been removed

  • Anonymous
    March 09, 2006
    Wow, a lot of passionate people about sample code!  I don't think it is worth getting abusive over.  Relax, this is about sample code.......

    I code in both but prefer C# for a couple of reasons.

    Firstly I find the code a lot easier to read/write because it is no where near as verbose as VB.  

    Secondly there are more job opportunites.  I am surprised by Tom's statement about VB being used by the majority of programmers.   I would have thought the job opportunites would have been a good indicator of the industry preference.  Obviously not.

    Personally I would prefer to see the C# examples because it does save time in re-writes.  However, so long as there are examples I don't really care what language they're written in.

  • Anonymous
    March 10, 2006
    I haven't read every comment yet, so I hope this hasn't been mentioned already.  I would prefer all samples written in VB and here's why:

    Far more people use VB than C#, but apparently more employers are looking for C# developers than for VB.  Supply and demand!  Keeping C# developers in short supply means they can command better salaries than otherwise.  I am learning C# with the hope of eventually doing it professionally, and I know when to count my blessings.  Please, keep the samples coming in VB.

  • Anonymous
    March 11, 2006
    What language is the best of other languages on the visual studio.net 2005

    C#.net or VB.Net ?

  • Anonymous
    March 13, 2006
    Why use C++, C#, or VB?  Write the examples in assembly or machine language.  I would like to see an assembly.NET.

  • Anonymous
    March 13, 2006
    The comment has been removed

  • Anonymous
    March 13, 2006
    The comment has been removed

  • Anonymous
    March 14, 2006
    I very excited to see main examples in VB.Net. My company and our vendors all code in VB.Net. When I am looking for a solution, I won't even stop and look if it is in anything but VB. I admire those that write in C# and C++, however coding is like electricity, corporations need to follow the path of least resistence. In this case being VB.Net.

  • Anonymous
    March 14, 2006
    The comment has been removed

  • Anonymous
    March 14, 2006
    The comment has been removed

  • Anonymous
    March 15, 2006
    The comment has been removed

  • Anonymous
    March 15, 2006
    It should be interesting to see what Tom's response to this is
    [http://realworldsa.dotnetdevelopersjournal.com/mstools.htm]
    as the letter from the forum monitor says he is going to.

  • Anonymous
    March 15, 2006
    Microsoft decided to not explain what happened to the team that so far has done a great job supplying samples and toolkits, or what will happen to them if Tom Archer's blog is fact.
    They just asked us to stop discussing it.

    I am starting to think Tom's blog was fiction to please the masses. I have not seen any lack of C# examples or toolkits.

    So for now I guess there is no real answer as to what the effect Tom's Blog describes will be, or even if it was anything more than a message to please the masses.

  • Anonymous
    March 16, 2006
    The comment has been removed

  • Anonymous
    March 16, 2006
    Why do some C# people think they're so good when they can't translate to simple VB.NET?

    Some people can translate between about 15-20 programming and non-programming languages and they're not as arrogant as these C# wannabes.

  • Anonymous
    March 16, 2006
    The comment has been removed

  • Anonymous
    March 16, 2006
    The comment has been removed

  • Anonymous
    March 16, 2006
    Thanks Tom, for responding to this thread...
    [http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=293923&SiteID=1]

  • Anonymous
    March 16, 2006
    as for me, VB would apeal to most of the people. reasons may include, a lot of newbie's would preffer vb as their stepping stone because it is BASIC and it is easy to understand and to related with.

    The fact that more C++ apps are released rather than vb, in bigger markets. but how about to small players? Remember that VB is a RAD. And I think lot of programmers out there making their things to their clients would like to do jobs faster, and consider vb is somewhat, for me, is the most compatible language for Windows, especially when working with their office. VB is very popular since most programs being developed out there are not for really big releases, but for small and medium scale business.

  • Anonymous
    March 17, 2006
    My name is ASM and I am C++ maggot

    Read my post above to my exude

  • Anonymous
    March 17, 2006
    My name is Iani and I believe the entire excel calculation engine was rewritten in C# b/c slower managed code is better than C++. Who cares whats practical, I need to be trendy here.

    Where is my MsAccess.Net??? You said it would be here!!! I am waiting...

  • Anonymous
    March 17, 2006
    The comment has been removed

  • Anonymous
    March 19, 2006
    much much karma here guys....

    gone thru many vb apps before, continued to .Net and landed into a weird language, in which I didn't expect and am not feeling right and suited, COBOL. This makes me sick a lot, considering that I can not practice real programming.

  • Anonymous
    March 19, 2006

    you should provide samples in vb, c#, and c++

    no excuses.

    particularly c++ where there are subtle syntax issues

    and where is the c++ .net documentation??

    Do you want people to use managed c++ or not??

    why build a product/library if you won't document it

  • Anonymous
    March 20, 2006
    I forbindelse med min cabana session på de netop afholdte lancerings events havde jeg den fornøjelse...

  • Anonymous
    March 20, 2006
    You know what? How about thanking the developers who wrote all of these samples in the first place? Regardless of which language it was written in. MS could've easly said, ok guys, here's the APIs and the explanation, now have a nice day. The explanation of why VB over C# is valid. Though I would like more samples in C#, I'd rather have some of something rather than all of nothing.

  • Anonymous
    March 20, 2006
    I come from Asia, First i think that that is a interest topic, but after Read to the End , the discussion is change to ( C# vs VB.NET ) more then (Why so many examples in Visual Basic)....well, on my opinion, Different of C# & VB.NET, just syntax .
    I have a VB6 Background and now is VB.NET , i always go PScode, Sourceforge , Code-project Site etc.. i don't think VB.NET sample is more then C#, maybe inside microsoft.com only, with the partner site, ww.asp.net , gotdotnet.com, it still have vb.net or C# sample for selection.

  • Anonymous
    March 21, 2006
    The greatest language is norwegian. That settles it.

  • Anonymous
    March 21, 2006
    Samples - all supported languages required.

    C++ vs C# vs VB.Net
    I have to do this! Depends on what you want to do.

    C++
    + Speed
    + Smaller memory footprint
    + Concise code
    + Compatable/supported with kernel (drivers, system DLLs)
    + Direct hardware level access
    + History - proven professional expertise and prestige
    + Fewer runtime dependencies
    + Platform source code portability (incl. backward compat)
    + Difficult to learn (barrier to non pros)
    - Difficult to master
    - Difficult to understand (figure out what someone did)

    C#
    + Similar to C,C++ and Java in syntax
    + More object oriented than C++ or VB (purer)
    + Concise code
    + History - inherits from C/C++ - prestige
    + Managed code
    + Difficult to learn (barrier to non pros)
    - Difficult to master
    - Difficult to understand (figure out what someone did)
    - Not compatable/supported with kernel (drivers, system DLLs)

    VB.net
    + Managed code
    + Easier to master
    + Faster development cycles
    + Similar to VB in syntax
    - Easy to learn - allows non pros to dev code
    - History - inherits from VB - negative
    - Not compatable/supported with kernel (drivers, system DLLs)
    - Allows certain poor programming practices

  • Anonymous
    March 22, 2006
    As a VB.net "User" i prefer the VB Samples!
    I can't understand the "C#"- and "VB"-Code "war" I always thinking .net is .net.
    And as a vb.Net Developer I also take a look into C# samples to solve my problems ;-)

  • Anonymous
    March 22, 2006
    The comment has been removed

  • Anonymous
    March 22, 2006
    VB? C#?  What about VFP?
    I'd settle for more contextual help files.

  • Anonymous
    March 22, 2006
    I would like as many languages as the author of the article proficiently knows.  I would like to have the examples, many as can be done, at the end of the article and/or someway to "transform" the exmaples in the page between the languages I want.  When the article content allows.  I understand some code snippets in the article explanations would be specific and hard to dymanically switch, but hey YOU ARE Microsoft.  You can do anything.  My choice is more C#, if it matters, and (Iron) Python.

  • Anonymous
    March 23, 2006
    Settle down and get back to work!

  • Anonymous
    March 28, 2006
    I am really pleased to see more examples in VB.NET.  I am allergic to brackets and semi colons.  As soon as I see them my mind starts to drift.  Give me those friendly, happy VB codes thank you Microsoft!

  • Anonymous
    April 05, 2006
    I think VB is easy than other ones.
    It doesn't like C or C++.

  • Anonymous
    April 05, 2006
    I come back..
    Vb use iron
    so more and more people study  VB and not need message like C.

  • Anonymous
    April 05, 2006
    VB use iron so more and more people study it more easy and more people use Vb to fishion they work.

  • Anonymous
    April 28, 2006
    Do not forget about VBA developers.  VBA Developers will understand VB NET .

  • Anonymous
    June 10, 2006
    <a href='http://www.yahoo.com'></a>Thanks! http://www.insurance-top.com/auto/">http://www.insurance-top.com/auto/ <a href='http://www.insurance-top.com'>auto insurance</a>. <a href="http://www.insurance-top.com ">Insurance car</a>: auto site insurance, car site insurance, The autos insurance company. Also [url]http://www.insurance-top.com/car/[/url] and [link=http://www.insurance-top.com]insurance quote[/link] from site .

  • Anonymous
    June 10, 2006
    Thanks!!! http://www.insurance-top.com/company/">http://www.insurance-top.com/company/ car site insurance. [URL=http://www.insurance-top.com]home insurance[/URL]: auto site insurance, car site insurance, The autos insurance company. Also [url=http://www.insurance-top.com]cars insurance[/url] from website .

  • Anonymous
    June 10, 2006
    Hi! http://www.insurance-top.com/company/ car site insurance. auto site insurance, car site insurance, The autos insurance company. from website .

  • Anonymous
    June 25, 2006
    http://www.insurance-top.com/company/">http://www.insurance-top.com/company/ auto site insurance. [URL=http://www.insurance-top.com]home insurance[/URL]: compare car insurance, auto insurance, insurance car. [url=http://www.insurance-top.com]cars insurance[/url] from website .

  • Anonymous
    June 25, 2006
    http://www.insurance-top.com/company/ auto site insurance. compare car insurance, auto insurance, insurance car. from website .

  • Anonymous
    July 05, 2006
    PingBack from http://www.sexybikini1.info/blog/12/

  • Anonymous
    September 11, 2006
    vb examples are good for me

  • Anonymous
    October 06, 2006
    I came from heavy VBA development as an analyst to VB5 as an early developer. Then 6, then .NET, and finally for over a year now C#. Why the jump across? Well, primarily because C# developers flat out get paid more in general (might be because there are less of them, I dunno). Yet, once you get beyond that, I think its important to look past the fact that they compile into the same CLR, but how you get to that point. While, yes, it is still a preference debate, I think the C# development environment in VS lends itself to better to programming cleaner applications than VB.NET. VB is a very verbose language in some ways and in the VS environment has worse commenting capabilities over its C# counter part. And face it, all joking aside, if youre working with anyone but yourself (and even then) commenting is HUGE in an application's lifecylce. I also found, the greater my understand of OOP was, the less inclined I was to using VB.NET because it actually seemed more difficult to get done what I wanted to accomplish.

  • Anonymous
    March 11, 2007
    mmm.. nice design, I must say..

  • Anonymous
    March 19, 2007
    Chi ha fatto questo? E un buon posto per trovare le informazioni importanti!:)

  • Anonymous
    April 13, 2007
    Stupore! Amo questo luogo!:)))))))

  • Anonymous
    April 15, 2007
    Stupore! Amo questo luogo!:)))))))

  • Anonymous
    April 19, 2007
    C# and VB.net examples are both listed in www.java2s.com