Salakhetdinov Shamil
mcp2004 at mail.ru
Mon Nov 14 15:05:41 CST 2011
Hi Dan -- > I do prefer VB for at least one reason: > VB is not case sensitive while C# is. I'm not arguing - that's funny: I, personally, dislike VB.NET because it is *not* case sensitive :) (And I have been programming using VBA/VB6 for 10+ years). I can provide my reasoning but would it make any difference there? BTW, there are many "indirect signs" that C# is "superior" than VB.NET, e.g. DotNetNuke code base moved from VB.NET to C#, as well as another large commercial Internet shopping applications I have worked with... Why they did that? Recap: when moving into .NET development from any other system I'd recommend to use C#. If you have already a large code base developed using VB.NET then you should be safe to continue using VB.NET. Thank you. -- Shamil 14 ноября 2011, 18:29 от "Dan Waters" <df.waters at comcast.net>: > I disagree on automatically taking the plunge on C#. > > The two languages, vb.net and C# are now, with .Net 4 and Visual Studio > 2010, almost identical, and MS will probably make them absolutely identical > in one of the next versions. As a relative newcomer, you won't see the > differences for a while. So, because there is no intrinsic advantage for > either language, it's just your personal preference. In addition, I've > found that the more I write in VB, the easier it is to read something in C# > and understand what's happening (converting code and comparing line for line > helps with this as well). > > Also, I've been programming in VB.Net for about 6 months, and have never not > been able to find examples using VB.Net. In fact, I'd say that about 40% > are in VB.Net, and the rest in C#. If you find an interesting example in > C#, you can usually convert it here: http://converter.telerik.com/. > Sometimes I will suffix my searches with '-C#' so that only VB.Net examples > come up, and I can more quickly get what I'm looking for. > > Of course, if you are going to be programming within a group of C# > developers, then you need to learn the language. If you're going to be > programming on your own, which it sounds like you're doing, then I'd say > skip the 'tiny brain exploding transition' and start with VB.Net. That's > plenty of a learning curve just with the transition to any .Net language. > > I do prefer VB for at least one reason: VB is not case sensitive while C# > is. For example, the variable 'stgPerson' in VB is the same as when you > type 'stgperson'; VB will change the case for you. But C# sees 'stgPerson' > and 'stgperson' as two separate variables, and I don't see how that would be > helpful. > > Many C# developers will often say that 'C# rules the world' and so on. Not > true. I think it's the same attitude that IT people have for Access. They > want to be 'superior' and do the 'true' language. The truth is it's not > that simple. > > You might want to write a small app in both languages, and see which one > works for you. > > It's been a while, but I believe that there are separate VS 2010 Express > downloads for each of the different languages. > > Good Luck! > Dan > > -----Original Message----- > From: dba-vb-bounces at databaseadvisors.com > [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Doug Steele > Sent: Sunday, November 13, 2011 10:00 PM > To: Discussion concerning Visual Basic and related programming issues. > Subject: Re: [dba-VB] Which version of Visual Studio > > Apart from anything else, I think you should just take the plunge and start > using C#. It appears to be the language of choice for .Net developers. > Whenever you search for for .Net programming advice on the web, 99% of the > explanations and examples will be in C#. > > The transition from VB to C# will be, from my experience at least, a tiny > part of the brain exploding transition from Access/VBA to .Net. > > And if you're thinking of making web apps, my advice would be to start right > in using MVC3. I built a couple of apps for clients using ASP.Net Webforms, > and I found the whole system to be really difficult to work with. > I thought it was just my advanced years and calcified brain, but I've > started working with MVC and it is, to my mind, much more straightforward. > > Doug > > On Sun, Nov 13, 2011 at 6:00 PM, newsgrps <newsgrps at dalyn.co.nz> wrote: > > > Ok - Here goes for my first post to this group. > > > > I currently have Visual Studio 2005 Professional installed which I > > have done some playing around on. I know this is getting a little old > > (like me). I am wanting to get more familiar with dot net and > > application development. > > > > Should I continue to use this to get more familiar with the dot net > > environment or should I get a later version (if so which one?). What > > are the advantages/disadvantages of each approach (apart from cost > > which is a big disincentive). The Express Visual Studio 2010 products > > don't seem to have enough features (for example the one dot net web > > application I do support is in vb.net but VS 2010 Express > > documentation doesn't seem to indicate that vb.net is included). > > > > Regards > > > > David Emerson > > Dalyn Software Ltd > > Wellington, New Zealand > > ______________________________**_________________ > > dba-VB mailing list > > dba-VB at databaseadvisors.com > > http://databaseadvisors.com/**mailman/listinfo/dba-vb<http://databasea > > dvisors.com/mailman/listinfo/dba-vb> > > http://www.databaseadvisors.**com <http://www.databaseadvisors.com> > > > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > >