Re: VB6, VB2005, or Something Else?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:V4ednSKiyce9LNLZRVn-jQ@xxxxxxxxxxxxxxx

While disappointed in dotNet's over-all sluggishness compared the VB6, I
was
heartened a bit to discover that a B# application is susceptible to some
positive performance tweaking. I was even lulled into thinking maybe MS
would eventually get it 'right'. Only to run into the new VS2005. - it is
slow! (Make that SLOOOOOOOOOW!)

I have no doubt that dotNet (or dotNext) will eventually be beneficial to
the "power" you can add to an app. Problem is, from my POV, I need
performance... iow, I want that CPU hogging/Single threaded app to run as
fast as the current hardware will let it run. All of the "scalability", etc,
features just aren't important here.... yet. They may be in the future
(possibly tying several machines together for SCADA or multi-step process
purposes) but right now, we have to be able to squeeze every drop of
performance we can out of what we have. dotNet just doesn't do it for us at
this point. As the only surviving "VB Guy" here, I have to be able to
communicate with existing libraries written in C6 (not VS6) and the "C Guys"
are complaining about speed (most of all) and the loss of their header files
(etc) in a dotNet migration

Ninty percent of your time is spent wondering what in the H*ll is it doing
now?

I still have no clue <g> Even with registry/process monitors crunching away,
who knows what's going on <g> fwiw, "some windows update" effected all of my
Office apps at work too. The most annoying (tooth grinding, chalkboard
scratching) problem I now have is the open file dialog in Office. Clicking
the down arrow to reveal the list of drives, etc is ridiculously slow....
about 30 seconds (or more!) to get the dropdown to show. Then, another 20+
seconds for each level you need to drill down in a folder structure. It
wasn't long before I switched to browsing to the file and double-clicking to
open.... but sometimes, I accidentally want to open another file from within
Office... the fun starts there <g> Thing is, no hard-drive activity, CPU's
not pegged, who knows what's causing the delay (other than some Windows
Update) Drives me nuts. 3ghz PC w/1gig ram. 30 seconds to open a dropdown?


--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm


.

Relevant Pages

  • Re: Sqlserverce class not working when VB.Net application is running from network drive
    ... The issue is that if more than one app attempts to connect to a sdf file on a network share, the first app that connections opens that file with an exclusive handle so no other apps can access it. ... >> possible that the database is already in use when you attempt to ... >>> network drives. ...
    (microsoft.public.sqlserver.ce)
  • Re: Whered that go then ..?
    ... with modern OS's) some order to the drives / data etc. ... spent six years as IT manager in charge of Windows ... boot off the install CD and do a reinstall ... app will still understand them). ...
    (uk.comp.sys.mac)
  • Re: Loading VB files?
    ... How 'bout finding something that'll get VB6 source from an app it ... does it take to start the first dotNet app of the day?... ... functionality", mmmkay? ... tells me these "knowledge or skills" are about 15 years behind... ...
    (microsoft.public.vb.general.discussion)
  • Re: Read Only flag is set on all folders on all drives.
    ... or command prompt is set to open at a default location ... (Quickbook is the *only* app that still checks RO on a directory AFAICR) ... >>> that all folders on all drives have the read only flag ...
    (microsoft.public.windows.file_system)
  • RE: cd writer does not recognize blank cd
    ... For my two optical drives, the DVD/CD combo drive the # in the value data ... I would use only the Recordnow app if it's ver 6 or better.. ... Also, and please answer this question for me, what burning app did HP ...
    (microsoft.public.windowsxp.hardware)