Jim Lawrence
accessd at shaw.ca
Mon Mar 15 13:59:16 CDT 2010
I full-heartedly agree with you. The basic creation of the .Net infrastructure was to allow the designer to write code in any way they want. There are dozens of CLI languages that can be used and if you are extending you applications to the web the count increases dramatically. You can mix and match within a single app...Any mashup that can get an application running http://en.wikipedia.org/wiki/List_of_CLI_languages The argument that one language runs faster than another is simply not true; any longer. My thought is use what ever language feels good to you or has the most 'field tested' code and has the features you need. Single language apps are the old way of thinking. Show me what an application can do and frankly I could not care less what it was written in. It is similar to saying English is better. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Monday, March 15, 2010 8:30 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] SPAM-LOW: Treeview/Listview OCX Disabled by MS Well, gentlemen, I stand by VB.Net since I absolutely hate the C# syntax and "punctuation". I can read it, but I don't want to write it. Of course, since I'm old enough not to have to expect to keep doing this, I can indulge myself by NOT learning C#. I do rather object to the avalanche towards it in the VB list, though. Seems like the fact that the language isn't the important thing gets forgotten. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Saturday, March 13, 2010 8:28 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] SPAM-LOW: Treeview/Listview OCX Disabled by MS I second pretty much everything William said, EXCEPT that I did not find C# syntax all that trivial to pick up. But like William I forced myself to do it and I am happy I did. John W. Colby www.ColbyConsulting.com William Hindman wrote: > ...vb.net and c#.net are virtually identical in their capabilities ...only > the syntax is significantly different in the latest versions and you'll pick > that up fairly quickly ...learning the net framework is the major effort, > not the language you choose to work in ...I started in vb.net because the > syntax seemed more familiar but that's really an illusion since it's very > different from vba in reality ...I've since moved to forcing myself to work > in c#.net because 1) that's where the work is and 2) that's what ~70% or > more of the on-line responses and sample code are written in ...and I live > on sample code ...besides which, there are some very good (and free) on-line > translators between the two now ...if I were starting over in net I'd pass > on vb.net and go straight to c#.net > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com