Hi Frustrated,
First you can't distribute those dlls. I don't think distribution is covered
in the license agreement and anyway a windows update will blow your versions
of those dll's away!
Second as a VS project you will have dependencies for the .Net framework
(whatever version 2?). Only WinXP pro is distributed with the .net framework
and most shareware distributors require you to link to a .net framework
download for the 50Mb of support files required!
Have a look at thecounter.com for an idea of the numbers and versions of IE
that are on the web to decide what your target market version is. This
should narrow you down to v5 and 6. You will have to use error trapping
inside your app to handle any differences in the object models for those
dlls between versions. I don't think shwdocvw.dll has changed at all between
versions 5 and 6 of IE (XP uses a different mshtml.dll version) so it should
be ok so long as you target those versions.
Most important of all....test test test and then test again. You will
realise then why it has taken so long for MS to progress with V7 of IE.
Regards.
"frustrated_developer" <(E-Mail Removed)> wrote
in message news

6C72A3D-5C5A-445D-AD33-(E-Mail Removed)...
> Hi,
>
> I have an application that uses shdocvw.dll, interop.shdocvw.dll,
> AxSHDocVw.dll, meaning in my Visual Studio project I had to created
> references with these dlls. My questions is, how is the correct way to
> distribute the application with these dlls so that it's compatible with
> Internet Explorer 6.0 on the Win XP, Win 2000, and Win 98 operating
> systems?
> Thanks.