-
I have created a web browser using the web browser control. Everytime I use the package & deployment wizard, it tells me that there isnt any dependency info for the wininet.dll.
If I attempt to install using the setup.exe, I recieve an 'access violation' with the wininet.dll I am checking for version syncronization in my program.....When the app is closed, I access the web and download a textfile via FTP. I was using the Internet Transfer Control, but I learned that there are bugs. So now I am using API calls to access the web via FTP, but still recieve the same error. My project is supposed to be available for beta-testing starting today. Please Help ASAP.
Thanks
dubi
-
wininet woes
i'm not saying this will work for sure but i remember having the same problem trying to install wininet on a machine that had outlook and i got nothin but grief. Finally just removed wininet from the setup package and it worked fine. wininet is NOT a COM DLL. That means good 'ol regsvr32 does not work. It's my hunch that when the PDW tries to install wininet it may attempt to register it(which can't be done) and then you end up with an error.
Don't make this mistake: I rebooted the NT machine to unlock all DLL's i needed, backed up the existing wininet.dll and then removed it(bad mistake number 1); then i copied the one i 'thought' i wanted onto the machine(bad mistake number 2) and my app worked fine so i declared it job done and left(bad mistake number 3, didn't test Outlook...)
A few minutes later the user called and said outlook did not work anymore... make a long story short i ended up replacing the original wininet, reinstalling my app without the wininet included in the package and both ended up working.
I'm not saying it's a rule of thumb to never include wininet, just saying that that's what worked THIS time.
If you're just uploading and downloading files, what went wrong with the Inet control?(and I know it's got it's own 'issues' as well, i'm just curious which ones)
-chris
Edited by pvb on 03-09-2000 at 12:13 PM
-
Thanks for the response Chris. Sorry to hear about the mishap with Outlook. I'll try n' remember not to overlook similiar scenarios. I figured the Inet control was the problem because there is known bug in the Inet control when using both FTP and HTTP protocols. It apparently only affects IE5. Only. So I figured thats where my problem was. I'll try and do it again, this time without any calls to the wininet.dll
Thanks Again
Dubi
