Re: WinINET API... Yay or Nay?
From: TJ (X_CentralWare_at_yahoo.com)
Date: 08/11/04
- Next message: Randy Birch: "Re: WinINET API... Yay or Nay?"
- Previous message: George Hester: "Re: VB6.0 to VB.NET"
- In reply to: GSM: "WinINET API... Yay or Nay?"
- Next in thread: George: "Re: WinINET API... Yay or Nay?"
- Reply: George: "Re: WinINET API... Yay or Nay?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Aug 2004 21:23:29 -0400
Dear GSM,
Just an opinion, mind you:
From my experience using iNet, you may want to consider doing a
file-check to ensure msinet is even installed (98% of the time it will be
since IE is in) however you will want to also do version checking of the
files to ensure they comply to the functions you're trying to access within
them. (I don't know the Win98/SE minimum versions off the top of my head -
it wouldn't be too difficult to extract them from the old 98 CDRom.)
Once you verify iNet is installed and it meets or exceeds your needs,
run a WinSock test to ensure 2.x is installed. This mainly applies to
Win95A, B and C however early releases of Memphis are affected as well since
sockets v2.x were still in the makings.
When you're testing - be sure that your API declares have a home in a
CLASS that can be called instead of in a module to prevent errors before you
even go to access the iNet API. (In VB - some can be trapped beforehand,
MOST however once the declares are already called will GPF the VB
application.)
Call example:
function TestMyPC() as Boolean
if(TestINet) = false then exit function
if(TestWinsock) = false then exit function
TestMyPC = true
end function
Call TestMyPC from the MAIN() startup module - if successful, then continue
loading otherwise show a message box.
In your iNet related form(s) simply create an instance of the API class such
as:
Dim MyAPI as new clsINetAPI or
Dim Withevents MyAPI as new clsINetAPI depending on weather or not your
class has events.
Hope this helps!
TJ
"GSM" <gsm00@hotmail.com> wrote in message
news:%23WMW5jzfEHA.1048@tk2msftngp13.phx.gbl...
> Hi,
>
> A few years ago, I looked into accessing files over the internet (HTTP and
> FTP protocols, specifically) using the WinInet API functions. However,
after
> looking into this for a while (and reading a few horror stories), I
> determined that the WinInet API was too unstable and unreliable to use.
> Eventually, the project was dropped.
>
> Fast-forward to three years later (now) I need to write an application
that
> will download files over HTTP and FTP. Is the WinINet API still considered
> buggy, or is it pretty reliable?
>
> One difference is that this time around, we will not support Windows 95.
> Windows 98 or later will be required. If I remember correctly, a good
number
> of problems with WinInet occurred on machines running Windows 95...
>
> This brings me to my second question, regarding deployment. The other
reason
> that using WinInet posed a problem three years ago is that it would have
> made the deployment of our app a real nightmare. Because we will only be
> supporting Windows 98 (which I believe ships with Internet Explorer 4.0)
and
> up, would this still be an issue? would we need to redistribute any DLL's
> (or anything else) with our app if we went the WinInet route this time
> around?
>
> Thanks so much for your help. I appreciate any advice/pointers you can
give
> or experiences you can share.
>
> Best regards,
>
> GSM
>
>
- Next message: Randy Birch: "Re: WinINET API... Yay or Nay?"
- Previous message: George Hester: "Re: VB6.0 to VB.NET"
- In reply to: GSM: "WinINET API... Yay or Nay?"
- Next in thread: George: "Re: WinINET API... Yay or Nay?"
- Reply: George: "Re: WinINET API... Yay or Nay?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
