Client side VBScript?

[David Zajac]

If this off-topic please accept my apologies.

With .NET around the corner, I haven't been able to find a definitive answer
regarding the future of client side VBScript as we know it. We have started
to build a large library of interactive electronic technical manuals that
are extremely dependent upon client side VBscripts and custom client side
ActiveX controls. Is our library in any jeopardy of not being viewable in
future versions of Explorer? NOTE: these documents are neither web-based
nor safe; they are installed on the user's local drives and through the
ActiveX controls access the user's I/O ports.

[Dan Barclay]

David,

On Tue, 10 Oct 2000 14:21:20 -0500, "David Zajac" <dzajac@Hiwaay.net>
wrote:

>If this off-topic please accept my apologies.
>
>With .NET around the corner, I haven't been able to find a definitive answer
>regarding the future of client side VBScript as we know it. We have started
>to build a large library of interactive electronic technical manuals that
>are extremely dependent upon client side VBscripts and custom client side
>ActiveX controls. Is our library in any jeopardy of not being viewable in
>future versions of Explorer? NOTE: these documents are neither web-based
>nor safe; they are installed on the user's local drives and through the
>ActiveX controls access the user's I/O ports.

It's a very good question, but I don't know the answer. In fact, at
this point I doubt you'll find anyone who can give you an answer with
a straight face. On the surface, VB compatibility and support for
existing apps seems to be very low on the priority lists.

Dan
Language Stability is a *feature* I wish VB had!
(#6)

[Rob Copeland [msft]]

Your library will continue to work, as Internet Explorer will continue to
support VBScript and ActiveX controls.

-Rob Copeland

"David Zajac" <dzajac@Hiwaay.net> wrote in message
news:39e36916$1@news.devx.com...
> If this off-topic please accept my apologies.
>
> With .NET around the corner, I haven't been able to find a definitive
answer
> regarding the future of client side VBScript as we know it. We have
started
> to build a large library of interactive electronic technical manuals that
> are extremely dependent upon client side VBscripts and custom client side
> ActiveX controls. Is our library in any jeopardy of not being viewable
in
> future versions of Explorer? NOTE: these documents are neither web-based
> nor safe; they are installed on the user's local drives and through the
> ActiveX controls access the user's I/O ports.
>
>
>
>

[David Zajac]

Well that's definitive! Thanks!


"Rob Copeland [msft]" <robertco@microsoft.com> wrote in message
news:39e3ac86$1@news.devx.com...
> Your library will continue to work, as Internet Explorer will continue to
> support VBScript and ActiveX controls.
>
> -Rob Copeland
>
> "David Zajac" <dzajac@Hiwaay.net> wrote in message
> news:39e36916$1@news.devx.com...
> > If this off-topic please accept my apologies.
> >
> > With .NET around the corner, I haven't been able to find a definitive
> answer
> > regarding the future of client side VBScript as we know it. We have
> started
> > to build a large library of interactive electronic technical manuals
that
> > are extremely dependent upon client side VBscripts and custom client
side
> > ActiveX controls. Is our library in any jeopardy of not being viewable
> in
> > future versions of Explorer? NOTE: these documents are neither
web-based
> > nor safe; they are installed on the user's local drives and through the
> > ActiveX controls access the user's I/O ports.
> >
> >
> >
> >
>
>