Why am I getting "Object reference not set to an instance of an object."?
If after copying the .browser file into your AppBrowsers folder you get a compile error “Object reference not set to an instance of an object.” and you have .NET 3.5 SP1, then the issue is likely that you must create a sub-directory (of any name) in your
Browsers folder and place the .browser file in there. E.G. \App_Browsers\MobileBrowserData\mobile.browser
How do I deploy the .browser file at the machine level?
If you add new browser definition files to the global directory or if you make changes to global browser definition files, those changes have no effect until you manually recompile the browser capabilities collection using the Aspnet_regbrowsers.exe tool, available
in the %SystemRoot%\Microsoft.NET\Framework\version folder, or programmatically cause recompilation by using the BrowserCapabilitiesCodeGenerator class.
if you are adding this .browser file to the global directory you
place it in a sub folder
for .NET to include it. E.G. %SystemFolder%\Microsoft.NET\Framework\v2.0.50727\CONFIG\Browsers\MobileDeviceBrowserFile\
I found an error in your data, how do I submit a bug?
Please use the Issue Tracker to submit your bug, please follow the steps outlined here:
How to submit a bug
I submitted a bug, when will it be fixed?
The bug will be investigated and triaged with other submissions. Fixes will be shipped periodically with every release of the .browser file.
Why is the .browser file so large?
The .browser file supports over 400 devices currently present on the market. The sheer amount of data required for that accounts for the .browser file's size.
A new device has been released to the market, when will you add support for it?
If a new device is available and it’s not in the current release please use the Issue Tracker and supply the device manufacturer and device name. We will try to find capability data for this device and include it with the next release.
Why does my application crash with “Parser Error Message: The 'parentID' attribute must be specified on the 'gateway' tag.”?
Most likely, your application is running on an earlier version of the .NET framework that does not support our
. Please ensure that you have
.NET Framework 2.0 Service Pack 2
installed on your machine (see
). If your application is hosted by Microsoft IIS, make sure that it is configured to use ASP.NET 2.0 or greater and not ASP.NET 1.1.