Microsoft Antivirus API enables software developers to develop applications that scan Microsoft Office documents before opening them. The Antivirus API also supports scanning Microsoft IE code downloads, such as ActiveX controls.
You can check that avast is not listed on Microsoft Office applications:
On the Menu Tools > Macro > Security
You can see, if you used sometime, TrendMicro, Inc.
F-Secure Client Security and Symantec AntiVirus were not implemented too…
If you said so, I believe you… just wondering that API would be a good feature.
Btw, any news from the new version (not build) of avast? Will it be 4.5 ? 8)
I think it’s just a matter of marketing. And Microsoft is the king of marketing. If a company wants to sell more products, they should be compatible with the maximum of Microsoft features, even if it is useless !!
My opinion is : if implementing Microsoft’s API doesn’t cost too much, do it !!
Yes, still scheduled for summer. But It’s not going to be something revolutionary – just evolutionary, I’d say… Couple of new features, couple fo bugfixes, even better stability…
avast 5 will eventually be something quite different but that’s still a long way to go…
I believe there will be some betaversions again before 4.5 is released (and I’m sure you’ll be happy to test some of the new features :)) - but I guess there’s not much to do right now.
Technical, as I explained earlier, yesterday we have added another huge bunch of Trojan-gen detection. Acutally, the number of false alarms was not so high - most of the files sent were real Trojans or some shadow programs (adware, game keyloggers etc). Not big trouble - and we will release the updates with those few removed soon!
I know Pavel… I recognize your efforts. But it’s terrible to found your computer after a scheduled scanning with a lot of files in the Chest. For me, eight scripts were moved to Chest and a lot of backup programs (the setup files)… It’s annoying.
After almost one day, the VPS is still 424-0