IE7. Any word about the affect on vbs.

A recent blurb in pcMag says that IE7 is much more secure than
IE6 ever was, and the major means by which the "improvements"
were achieved was by stifling scripting and actX objects.

Further, it went on to say the IE7 would most likely "break"
(does that mean render inoperable?) a vast number of websites,
and "break" an even vaster number of intRA-net web applications
(leading one to presume that intRA-net apps make a greater use
of scripting than the public websites).

The conclusion was that microsoft was frantically distributing
IE7 betas (or release candidates?) so that their customers could
reprogram their websites and their internal net-based apps to
conform with the requirements of IE7.

It is understandable that microsoft would want to stifle scripting,
those evil and malicious scripters have been giving everybody agita.

However, the customary advice given here to anybody who wishes to
have a scripting GUI is to script yourself up a suitable dialog
using the automation interface to IE6.

So finally, here's the question. Are all those scripts (or hta's)
going to be "broken" by IE7 also???

cheers, jw

Dave
Tue Mar 14 17:26:53 CST 2006

Hi jw,
It's not correct that IE7 will 'likely "break" (does that mean render
inoperable?) a vast number of websites'
Most websites and applications render jsut fine in the currently available
preview and are expected to in the final release as well. You can get teh
preview at http://www.microsoft.com/windows/ie/ie7/default.mspx
The cases where an update to the site is necessary due to the improvemetns
in IE7 are outlined at
http://msdn.microsoft.com/library/default.asp?url=/workshop/essentials/whatsnew/whatsnew_70_sec.asp

Thanks
-Dave


"mr_unreliable" <kindlyReplyToNewsgroup@notmail.com> wrote in message
news:OIdONL7RGHA.5808@TK2MSFTNGP12.phx.gbl...
>A recent blurb in pcMag says that IE7 is much more secure than
> IE6 ever was, and the major means by which the "improvements"
> were achieved was by stifling scripting and actX objects.
>
> Further, it went on to say the IE7 would most likely "break"
> (does that mean render inoperable?) a vast number of websites,
> and "break" an even vaster number of intRA-net web applications
> (leading one to presume that intRA-net apps make a greater use
> of scripting than the public websites).
>
> The conclusion was that microsoft was frantically distributing
> IE7 betas (or release candidates?) so that their customers could reprogram
> their websites and their internal net-based apps to
> conform with the requirements of IE7.
>
> It is understandable that microsoft would want to stifle scripting,
> those evil and malicious scripters have been giving everybody agita.
>
> However, the customary advice given here to anybody who wishes to
> have a scripting GUI is to script yourself up a suitable dialog
> using the automation interface to IE6.
>
> So finally, here's the question. Are all those scripts (or hta's)
> going to be "broken" by IE7 also???
>
> cheers, jw

Dave
Tue Mar 14 17:32:51 CST 2006

I shoull also add that the IE team blog at http://blogs.msdn.com/ie is a
great place to keep up to date on IE progress.

Thanks
-Dave


"Dave Massy [MSFT]" <DMassyMSFT@Discussions.microsoft.com> wrote in message
news:%23sTII77RGHA.4956@TK2MSFTNGP09.phx.gbl...
> Hi jw,
> It's not correct that IE7 will 'likely "break" (does that mean render
> inoperable?) a vast number of websites'
> Most websites and applications render jsut fine in the currently available
> preview and are expected to in the final release as well. You can get teh
> preview at http://www.microsoft.com/windows/ie/ie7/default.mspx
> The cases where an update to the site is necessary due to the improvemetns
> in IE7 are outlined at
> http://msdn.microsoft.com/library/default.asp?url=/workshop/essentials/whatsnew/whatsnew_70_sec.asp
>
> Thanks
> -Dave
>
>
> "mr_unreliable" <kindlyReplyToNewsgroup@notmail.com> wrote in message
> news:OIdONL7RGHA.5808@TK2MSFTNGP12.phx.gbl...
>>A recent blurb in pcMag says that IE7 is much more secure than
>> IE6 ever was, and the major means by which the "improvements"
>> were achieved was by stifling scripting and actX objects.
>>
>> Further, it went on to say the IE7 would most likely "break"
>> (does that mean render inoperable?) a vast number of websites,
>> and "break" an even vaster number of intRA-net web applications
>> (leading one to presume that intRA-net apps make a greater use
>> of scripting than the public websites).
>>
>> The conclusion was that microsoft was frantically distributing
>> IE7 betas (or release candidates?) so that their customers could
>> reprogram their websites and their internal net-based apps to
>> conform with the requirements of IE7.
>>
>> It is understandable that microsoft would want to stifle scripting,
>> those evil and malicious scripters have been giving everybody agita.
>>
>> However, the customary advice given here to anybody who wishes to
>> have a scripting GUI is to script yourself up a suitable dialog
>> using the automation interface to IE6.
>>
>> So finally, here's the question. Are all those scripts (or hta's)
>> going to be "broken" by IE7 also???
>>
>> cheers, jw
>
>

mayayana
Tue Mar 14 22:59:23 CST 2006



> A recent blurb in pcMag says that IE7 is much more secure than
> IE6 ever was, and the major means by which the "improvements"
> were achieved was by stifling scripting and actX objects.
>
There's an interesting explanation here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/IETechCol/c
ols/dnexpie/activex_security.asp

If you read the details you'll see that it's actually not
very different from the current scenario, except that
unknown ActiveX controls will not run without prompting.
Previously used controls, Windows standard controls,
and any controls that have been marked safe in a new
Registry "PreAprroved" key will still run.

> However, the customary advice given here to anybody who wishes to
> have a scripting GUI is to script yourself up a suitable dialog
> using the automation interface to IE6.
>
> So finally, here's the question. Are all those scripts (or hta's)
> going to be "broken" by IE7 also???
>
I suppose it would change things if HTAs were disabled,
but what difference does higher security make otherwise?

As it is now, people with XP SP2 , and most people with
recent versions of anti-virus, already have to understand
and change their settings if they want to use script. (Norton
now has a special function just to block scripts, which
doesn't apply to EXEs!)

Beyond that, IE7 is still apparently a ways off and will only
run on XP SP2, anyway. So.... sometime next year, some
people with XP SP2 will probably have to make *further*
adjustments in order to keep running VBScripts without nag
warnings.