[AccessD] VB.NET

As to the 'javascript' issue:  to respond to a client-side event, you'd have
to write your own javascript anyway -> .Net simply does this for you, which
is great for guys like me who aren't keen on JS.  I can't see any security
risks involved off the top of my head.

Whats more is that .Net automatically determines if the browser supports
'uplevel' features, and if not, alters the client side code that it creates
to suit.

But, the main advantage for me is maintaining state automatically.  A common
scenario:

"You need a web-form which displays existing data from a record, allows
editing of those details and must validate the details upon submission
before saving".

In most languages you need to write one set of code to initially populate
your fields, another to collect the user data after form submission, and yet
another to validate the code and re-populate those fields if validation
fails.

In .Net, you populate your fields once, and apply appropriate validation
rules to them.  

ASP.Net will then perform this validation server-side and/or client-side (if
the browser supports it) *automatically*, and if the validation fails, will
re-populate the fields *automatically* (through a feature called
'viewstate').

I can't think of anything that beats that... It ensures validation is
carried out irrespective of the browser version, and maintains state as if
it were a real-time thick-client application like Access or a Windows
Application.

That in itself is worth a look in my book...

Cheers,
Andrew

 
-----Original Message-----
From: DWUTKA at marlow.com [mailto:DWUTKA at marlow.com] 
Sent: Wednesday, 2 June 2004 7:07 AM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] VB.NET

That's why I'm a little leary of ASP.NET.  Not so much about the latest
gadgets being able to use limited versions, but OLDER versions of a browser
that doesn't have a clue about a javascript line.

As for the VB/.NET comparison.  I agree that most of it is style related.
However, I would like to clarify a few things:

Initialize/Terminate: I see what you mean now, about sending arguments into
a class when created. I too have created many a class where I have built a
'GetData' or 'Startup' function to perform startup code, only after various
elements have been set.  However, that doesn't mean that VB 6.0's process is
flaky.  .NET has improved the capability, not the stability.  That is a BIG
difference in my book.

The Function/Sub bracket issue.  Um, I don't think I have used 'Call' since
the first few months of programming.  To me it's just obbvious, Standalone
no parenthesis required, as an 'argument' or on the right side of an
equation, then you use parenthesis.  I can see how forcing them to always be
there would make it 'consistent', in a manner of speaking, but to me that is
just a nuance.

As for API's, ya, I've found a lot of people shy away from API's.  It took a
few months to get into, but after that, I can't get enough of them.  I have
to agree the LoWord/HiWord issue is a little bit of a pain, but I have found
that the MSDN has documentation on every API (almost) that I have come
across.

I almost never use arrays, unless I am forced too.  An example of where I am
forced....Split().  It returns an array.  Since I have delved into
collections, I have never looked back.  Are you saying that .NET let's you
search AND sort collections?  Personally I 'build' my collection 'sorted' if
I need it to be, and if I need to search, I am usually creating the key off
of what I am going to most frequently be using as a 'search' key.

Haven't done much with serial comms in VB.  Just never needed too.

Over all, still nothing that blows my skirt up! <grin> (I know I'm going to
hear something about THAT comment! LOL)

Inheritance and the constructors sound neat, but there I have done without
for quite sometime.  It's not that I don't want to try it out, and get used
to it (cause I DID 'review' those movies, so my copies on it's way), but I
just have so much in my current 'model', it's just habit to kick stuff out
in that format.  Know what I mean?  Maybe I'll try tackling a few 'stand
alone' projects with it.

Drew



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Brett Barabash
Sent: Tuesday, June 01, 2004 3:55 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] VB.NET


My understanding was that it uses JavaScript to perform the custom control
behaviors.  My understanding was that the server renders it to something
that most browsers can accept.  I even saw a demo where an ASP.NET app
adapted its output to WML on a browser-enabled text-only cell phone.

Haven't delved far enough into this aspect to tell you exactly which
browsers it works with.

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

IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.