[AccessD] Moving to .Net (was Ded Moroz sends you ...)

I think it would be more appropriate to simply rename this list to "Access
to .Net", fold in the VB list and go from there.

Jim



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Monday, January 03, 2011 1:38 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Moving to .Net (was Ded Moroz sends you ...)

Can you guys take this disvussion over to the VB.  It's getting very long
and way OT for the 
Access list.

Cheers,
Stuart


On 3 Jan 2011 at 6:42, jwcolby wrote:

> The curly brackets really just replace begin / end keywords in VB. 
> They mark blocks of code.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> On 1/3/2011 4:01 AM, Gustav Brock wrote:
> > Hi Dan
> >
> > It appeared to me that to equip VB.NET with the same options than
> > C#, MS have had to push the VB (or BASIC) syntax beyond its original
> > intention: to be a simple language easy to learn and easy to use.
> > Even with my solid VBA background I found it difficult to read
> > VB.NET and I realised that a lot of learning was required. Given
> > this task, I wondered if this wasn't the time to learn something
> > really new to me, C#. Highly inspired by Shamil and the fact that
> > about 95% of all code you meet when you look for code and tutorials
> > about Visual Studio and .Net, and that the popularity of C# had to
> > have a reason, I made the decision to go for C#. As everyone, I had
> > a time struggling with the curly brackets, but once you get over it
> > and begin to see the picture of the code, that picture is a beauty.
> > I cannot explain it, but it just gives me more pleasure to write C#
> > than VBA. Well, one reason is probably that I find it more well
> > thought-out for the purpose - you really feel that this language is
> > written by programmers (actually some of the best of this world) for
> > programmers.
> >
> > This is just my opinion and preference. There really is no "best"
> > language - I still write a batch file now and then - and everyone
> > should pick what they like.
> >
> > /gustav
> >
> >
> >>>> df.waters at comcast.net 02-01-2011 22:26>>>
> > Hi Gustav,
> >
> > What was it about C# where you liked its syntax better than VB.Net?
> > Especially coming from a VB6/Access background?
> >
> > Also - in C# prior to 2010 version, how did you work around not
> > having optional parameters?
> >
> > Thanks!
> > Dan
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav
> > Brock Sent: Sunday, January 02, 2011 3:30 PM To:
> > accessd at databaseadvisors.com Subject: Re: [AccessD] Moving to .Net
> > (was Ded Moroz sends you ...)
> >
> > Hi Dan
> >
> > Don't know, but I did. And switched to C# to learn something new and
> > because I didn't like the syntax of VB.NET.
> >
> > /gustav
> >
> >
> >>>> df.waters at comcast.net 02-01-2011 19:48>>>
> >
> > .. But how many VB6 or Access developers (who loved VB6 and/or
> > Access) have moved to .Net?
> >
> >
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com