[AccessD] VB.NET

Actually, I watched some of the ASP.Net stuff, and the only 'impressive'
feature I saw was the ability to replace .dll's that are in use.  It's an
annoyance to restart and IIS server, but it's not that difficult really.  So
it's a neat trick, but it's not making me gear up for ASP.NET.  What I
REALLY want to know about ASP.NET, is how browser dependant is it?  They had
something VERY similiar to what you see as 'features' of ASP.NET in some
'remote' scripting language.  Can't remember the exact name. However, it
required IE, and IE only.  A lot of what ASP.NET is doing, is mimicing
features I read about a long time ago with the 'remote' scripting.  So I'm
just a bit cautious as to how 'wowie' asp tricks get.  We have users out
there with VERY old browsers....long story.

As far as the items I disagree with:

Haven't found Initialize/Terminate events to be 'flaky'.

(strongly agreed with the Dim x As New comment though...pure evil.  I used
it for a while, and didn't even know about it...)

I personally don't care to initialize variables when I'm declaring them.  To
me, that is more of a constant role, then an variable role.  I personally
prefer to declare my variables and then get to assigning them values.  I
think it helps me structure my code better.  By thinking only about what
variables I am going to need, I get a pretty good picture of the 'framework'
I am building.  I find that some of my best 'code' is when I don't have to
declare a variable 'mid stream'. (I'll declare it at top, but I mean:
'Ooops, need a variable for that...' kind of thing).

Not sure what you really meant with the bracket syntax for functions and
subs.  

Never found Win32 API's to be combersome.  Only quirk I have ever found are
the ones that require ByVal (which I also agree should be the default).

Have never found collections to be tricky to work with, and also have not
found them to be limited either.  (What limitations are you referring too?)

Used File I/O commands in VB pretty easily, but I think I use slightly
different syntax/commands then what I have seen on the list.

VB does have console support, it just can't output to it! LOL.  But if you
are writing batch files, you just need to be able to call it.  <grin>  (kind
of teasing on this one, I think it would be handy too.....I think I did find
something sometime that showed a way to create console output from VB).

Only real issue I have found with the services, is that the OCX does not
allow for multi-threading.  Other then that, I practically have a 'Windows
Service Project' for VB 6.0.  Practically drop in place (Actually, I usually
just grab one I built, and plop in the new code (depending on whether it's a
timer or 'event' driven service).)

Have never had 'unstable' issues with Multi-threading, but I will admit that
it is somewhat a pain to implement....well, somewhat is understating it a
little! LOL.

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 2:23 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] VB.NET


I'd be interested in knowing which ones you disagree with.  To gain
perspective, of course, not to stir up a heated argument <VBG>

(If you wanna talk about being wowed, try out the new ASP.NET features!)

Bryan, Andy et al:  I realize that this discussion is better suited to
dba-VB, but since the majority of listers aren't subscribed to it, I
purposely left it here.  I promise to let this thread die on my end by
sundown.