Re: Running Internet Explorer in App Verifier

Mr. Sullivan,

Thank you for your answer. Regarding a "clean" copy of IE, by now No Logo and your colleague Dan Mihai have posted their information and it's an old version of IE.

My next hope is that Microsoft's own drivers will be forced to go through the same process. At least applications are a start though. Thank you.

Yours sincerely,
Norman Diamond


"Brad Sullivan" <BradSullivan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:191F90C5-59B6-4779-BCDF-69B6C2371E78@xxxxxxxxxxxxxxxx
Microsoft applications will need to go through the same process as any other
to carry the "Certified for Windows Vista" logo. (IE isn't completely
applicable here since it is part of the OS, but it will be held to the same
standards.)

Most of the time, bugs found in IE are caused by 3rd party extensions like
ActiveX controls or toolbars. Since these run in the same process as IE,
they will look like IE bugs. If a 'clean' copy of IE is causing App Verifier
to break into the debugger, please report it.

Thanks,
Brad Sullivan
Program Manager
Windows Fundamentals

This posting is provided "AS IS" with no warranties, and confers no rights.

"Norman Diamond" wrote:

I agree with Joe. However, even though I only partly agree with No Logo, I
think she/he chose a name correctly. Microsoft ought to deny a "Designed
for Windows Vista" logo to Windows Vista. Also any computer that ships with
Vista preinstalled ought to be denied a logo.


"Joe" <joe@xxxxxxxxxx> wrote in message
news:%23119a%23ddGHA.3632@xxxxxxxxxxxxxxxxxxxxxxx
> IE and most of Windows don't get the benefit starting out with modern
> tools,
> concepts, etc. Backwards compatibility has always been a strong point
> with
> Microsoft products, they don't have a closed system like the other
> operating
> systems. People can install software from any source, software of
> questionable quality, but if it is truly useful and becomes widespread,
> even
> if it was buggy, it still has to work as the operating system gets
> upgraded.
> Windows XP and soon Vista are leading-edge, but you will probably still > be
> able to run your oldest Win9X apps.
>
> Because of this, not even Microsoft can take advantage of their latest
> technology. C++ is notorious for latent bugs being exposed as > compilers
> become more compliant. My own code had a mysterious failure when > moving
> from VC6 to X64 using the latest Platform SDK. My codebase is tiny
> compared
> to IE. The problem was -- I don't even know. One template class > deriving
> from another... most all classes using that pattern had no problem, but
> this
> one... recompiling with the latest compiler is the best way to break a
> working app.
>
> And IE is really part of the OS. It hosts functionality used by other
> software. If they re-compiled IE with their latest compiler, they > could
> probably get it to work in most cases. But, since 100%
> backwards-compatibility is the goal, "most cases" is not good enough.
> They
> way the do it is such that my computer system, with the 3rd party > software
> I
> have installed, with hardware from various manufacturers over the > years,
> the
> program I have been running for the past 10 years still works.
>
> So, yes, their core software will show problems that result from legacy
> code.
>
> But, new software should not have these problems. If you are in the
> position of being able to start a new project, you are lucky. Not so > with
> Microsoft and IE, and a lot of other code in Vista.
>
>
>
> "No Logo" <nologo-2006@xxxxxxxxxxx> wrote in message
> news:e41fml$lgp$1@xxxxxxxxxxxxxxxx
>> Hello all,
>>
>> I'm currently trying to test my application with the App Verifier
>> program.
>> It threw up all sorts of errors. Then, I ran IE in App Verifier and it
> also
>> threw up all sorts of errors. Why would this be? I would have thought
>> that
>> Microsoft would make sure that their own applications behave correctly >> in
> it
>> before dictating to everyone else who wants to apply for the Vista >> logo.
> Any
>> thoughts out there?
>>
>> Thanks in Advance,
>> No-Logo
>>
>>
>
>



.

Relevant Pages

  • Yesterdays Microsoft marketing bravado is just too funny. So now, 17 months after general availabili
    ... I have said again and again that Microsoft will be unable to revive the dead vista. ... The big talk and promises came from Microsoft's Worldwide Partner Conference, in Houston, where Brad Brooks fessed up about Vista marketing mistakes and promised there would be response to Apple's "Get a Mac" ads. ... Microsoft should never have abandoned the original "Wow" Windows Vista marketing campaign. ...
    (microsoft.public.windows.vista.general)
  • Re: Running Internet Explorer in App Verifier
    ... Microsoft applications will need to go through the same process as any other ... to carry the "Certified for Windows Vista" logo. ... I'm currently trying to test my application with the App Verifier ...
    (microsoft.public.win32.programmer.tools)
  • Re: Windows Vista at One Year (Dark Side Report)
    ... Shop manager Aaron Kaplan said they were prompted to put it up because so many people were having problems with Windows Vista, including compatibility issues with older software and trouble adjusting to the interface. ... Microsoft released Windows Vista to the world one year ago with ads likening the new PC operating system to such awe-inspiring moments as the first American spaceflight and the fall of the Berlin Wall. ...
    (soc.retirement)
  • Re: Why one should choose Linux over Vista
    ... Because you hate Microsoft ... It?s never too much for Vista! ... There is no Linux Genuine Advantage! ... DVD Burning Problem in Windows Vista ...
    (microsoft.public.windows.vista.general)
  • Re: Running Internet Explorer in App Verifier
    ... I am more familiar with App Verifier, independent of the Vista Logo ... What other tests do Microsoft carry out on software that complies to ...
    (microsoft.public.win32.programmer.tools)