This is because the browser definitions that were (appreciatively) borrowed from Ocean's Place are inheriting from definitions that existed on the .NET framework v2 and no longer exist on v4.There are two ways around this:
- Replacing all the definitions from .NET4 with the old ones from .NET2
- Remove Ocean's definitions
Replacing all the new definitions with the old ones worries me as we’d getting out of sync with the expectations of the framework, which will affect service pack updates to these definitions.



I am afraid to say that the new definitions in .Net4 are even worse at identifying bots, and older browsers. They removed support for older browsers, and mobile devices in this beta. It will identify IE,Firefox,Safari,Iphone,Blackberry's, and a few others but that pretty much some up what it will detect currently in the build I downloaded yesterday.
ReplyDeleteOcean
Thanks Ocean for the (bad) news ;) I have done some testing since I wrote this post and you're right: MS's new definitions fall way (way way) short of the level of detail that you put into your definitions (for .NET 2).
ReplyDeleteI noticed on your site that .NET4 definitions are on way. Can't wait. Let me know when they are available, I'd like to write a post about them.
Thanks, worked fine, i chose the second way around :P
ReplyDelete