Heenan, Lambert
Lambert.Heenan at chartisinsurance.com
Mon Jan 3 12:42:06 CST 2011
When you say that optional parameters are not needed in C# is that because you can just write a new method that has the same name but a different signature?
Long Foo() // this routine takes no parameters
Long Foo(Long x) // this routine takes one parameters
... Etc. etc.
Lambert
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov
Sent: Monday, January 03, 2011 10:08 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Moving to .Net (was Ded Moroz sends you ...)
Hi Dan --
As Gustav has noted here already - C# is a really beautiful programming
language: concise but very powerful and expressive.
If Gustav, JC, myself, William Hindman, ... are telling you: try it - and you'll never look back - why not try it? ;)
Curly braces will be an issue for you for a couple of days but later on you'll be wondering: "How did I program before without curly braces?"
You can line up curly braces whatever way you prefer, e.g.:
class Program { static void Main() { System.Console.WriteLine("Hello, World!"); }} // that supposed to be one code line but it could have been wrapped while getting through cyberspace...
Optional parameters: those are for "anarchical" programming style (sorry) - I used them quite a lot in VBA/VB6 but they are not needed in C#/VB.NET except for MS Office Automation...
Thank you.
--
Shamil
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: 3 ?????? 2011 ?. 5:51
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Moving to .Net (was Ded Moroz sends you ...)
Hi Shamil,
I'm using my perception of the syntax difference between the two languages to say the VB.Net is easier to use and quicker. I see much easier typing and easier code reading in VB.Net. I can type very quickly, but getting all those braces entered in and lined up on otherwise blank lines is clearly a waste of time and space on screen. Without all those blank lines I can see more code on one screen at a time - and for me that's time saving. I've also read that most programmers do agree that, all other things being equal, VB.Net is easier and quicker to use. With the 2010 versions be equal enough, I'm going to start in VB.Net 2010 version.
I've frequently used optional parameters in Access VBA for several years.
Honestly, I would be very frustrated writing several 'almost the same'
procedures. In a few procedures I've used many optional parameters - very helpful. Here's an example:
Public Function SendEmail(Optional ByVal stgTo As String, _
Optional ByVal stgSubject As String, _
Optional ByVal stgMessage As String, _
Optional ByVal blnBackup As Boolean, _
Optional ByVal stgBackupFunction As String, _
Optional ByVal stgAttachmentList As String, _
Optional ByVal blnDisplay As Boolean, _
Optional ByVal blnSendToCurrent As Boolean, _
Optional ByVal blnHideEmailNotice As Boolean, _
Optional varObjectType As Variant, _
Optional ByVal stgObjectName As String, _
Optional varOutputFormat As Variant, _
Optional ByVal stgObjectFileName As String, _
Optional ByVal blnExcludeOpenLink As Boolean) As Boolean
In your last paragraph you discuss full dynamic data binding in .Net 4.0.
This sounds like a powerful feature - I'll read up on this to see if there's a difference in the 2010 versions.
Thanks!
Dan
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov
Sent: Sunday, January 02, 2011 4:21 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Moving to .Net (was Ded Moroz sends you ...)
Dan --
C# syntax (IMO) is a natural for professional programmers' "thinking flow", it helps to think through and to program fluently, to define (and to scope) variables where they are really needed, ...
Optional parameters can be simulated by using similarly named methods with different sets of parameters - just one approach... (Optional parameters were originally introduced in VB not because of their being so useful but because of VB/VBA syntax (and implementation) limitations - and as it happens they got popular, and helped "chiseled in stone" COM (/MS Office) interfaces to evolve in time - that was a forced solution IMO for COM/MS Office to survive in business applications world....
In C# 4.0 (AFAIU) optional parameters were introduced mainly to simplify MS Office Automation programming. I mean there is no that much need in optional parameters when one programs on C# or VB.NET without using MS Office Automation.
Dynamic (late) binding was partially introduced in .NET 3.5 (C# 3.0) - 'var'
data type - and now in C# 4.0 there exists a full dynamic binding - 'dynamic' data type (you can see it's application in 'Ded Moroz...' samples) but this dynamic data type is not because of Visual Basic(.NET) influence - it's a much more powerful than in VB(.NET) - and it reflects the nowadays mainstream tendency of extending usage of dynamic languages...
Thank you.
--
Shamil
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: 3 ?????? 2011 ?. 0:27
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Moving to .Net (was Ded Moroz sends you ...)
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
--
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
--
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