On Mon, Oct 6, 2008 at 9:43 AM, Dave Crozier <[EMAIL PROTECTED]> wrote:
> John,
> I concur with the other group comments but would suggest that you seriously
> look at C# as opposed to VB.Net.
Agreed. Although I'm still starting out with .NET there seems to be
much more information out there on C# than VB.
> The execution speed is much superior and the OOP things you can do bear more
> of a similarity to VFP than VB.
Is the speed really different? I thought C# and VB were the same
language with different 'layouts'.
> My comments, so far, apart from the changed language syntax, having written
> some 20-30 C# applications are as follows:
>
> Pro:
> 1. My main gripe - Data Binding of Objects to UI classes are a pain in
> VS2005 unless you bind to a Datasource (VFP Cursor equivalent). You can bind
> an object property quite easily to a textbox for example but the
> relationship is one way only i.e changing the Control u[dates the object
> property but NOT Vice versa without a lot of messing about. This has been
> improved in VS2008 but is still nowhere as easy as in VFP. There is no
> concept of "Controlsource" as we VFPer's know it.
As I said, I'm still toying with .NET but I managed to bind objects to
gui elements fairly easily by implementing the INotifyPropertyChanged
interface.
My object has get/set methods like this:
private string _name;
public string name
{
get { return this._name; }
set { this._name = value; NotifyPropertyChanged("name"); }
}
A change to the object automatically updates the textbox etc.
> 5. I still can't get used to using a "==" as opposed to a "=" in an if
> statement and having to use != as opposed to <>. These still screw me up all
> the time. One other construct that is a pain is the VFP "Do Case" equivalent
> i.e Switch. You can forget about putting in case <....> statements that
> refer to any variable/function as you have to reference the variable(s)
> specified in the initial "Switch" statement.
I come from a C background so that's fine by me :-)
Currently I'm struggling with the fact that ASP.NET only supports
'connectionless' data. The idea is that you connect to the database,
get your data and disconnect. The problem
--
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
