mdbf Wiki & Documentation Rss Feed

Updated Wiki: Home

shanselman — Fri, 19 Aug 2011 22:27:21 GMT

Important Note: This project is no longer supported

There are alternatives and a good whitepaper to read at http://www.asp.net/mobile

Project Description
The Mobile Browser Definition File contains definitions for individual mobile devices and browsers. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.

This project provides a data file that when used with ASP.NET will detect the incoming mobile device and present you as the web developer with a set of 67 capabilities or properties describing the requesting device. These capabilities range from screen size to cookie support and provide all the information you need to adaptively render content for mobile phones and devices.

What is the Mobile Device Browser Definition File?
The Mobile Device Browser Definition File contains capability definitions for individual mobile devices and browsers. At run time, ASP.NET uses this .browser file, along with the information in the HTTP request header, to determine what type of device/browser has made the request and what the capabilities of that device are. This information is exposed to the developer through the Request.Browser property and allows them to tailor the presentation of their web page to suit the capabilities of the target device.

More Information
The format of the .browser file is XML and the schema is defined here: Browser Definition File Schema. The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the browserCaps element was used to define browser definitions in configuration files. Please note that you must have you must have Microsoft .NET Framework 2.0 Service Pack 2 installed to use this .browser file. See requirements...

Final Release Announcement 15-July-2010
Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th July 2010 and the final release on the 24th August 2010.
We would like to thank everyone who used our product over the past year and a half. We would also like to thank everyone who contributed to the discussions and raised issues on our data.
Final Release Discussion

Links

Updated Wiki: Home

shanselman — Fri, 19 Aug 2011 22:27:10 GMT

Important Note: This project is no longer supported

!!There are alternatives and a good whitepaper to read at http://www.asp.net/mobile

Project Description
The Mobile Browser Definition File contains definitions for individual mobile devices and browsers. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.

This project provides a data file that when used with ASP.NET will detect the incoming mobile device and present you as the web developer with a set of 67 capabilities or properties describing the requesting device. These capabilities range from screen size to cookie support and provide all the information you need to adaptively render content for mobile phones and devices.

What is the Mobile Device Browser Definition File?
The Mobile Device Browser Definition File contains capability definitions for individual mobile devices and browsers. At run time, ASP.NET uses this .browser file, along with the information in the HTTP request header, to determine what type of device/browser has made the request and what the capabilities of that device are. This information is exposed to the developer through the Request.Browser property and allows them to tailor the presentation of their web page to suit the capabilities of the target device.

More Information
The format of the .browser file is XML and the schema is defined here: Browser Definition File Schema. The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the browserCaps element was used to define browser definitions in configuration files. Please note that you must have you must have Microsoft .NET Framework 2.0 Service Pack 2 installed to use this .browser file. See requirements...

Final Release Announcement 15-July-2010
Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th July 2010 and the final release on the 24th August 2010.
We would like to thank everyone who used our product over the past year and a half. We would also like to thank everyone who contributed to the discussions and raised issues on our data.
Final Release Discussion

Links

Updated Wiki: Home

CodePlexAdmin — Mon, 27 Sep 2010 23:48:39 GMT

Important Note: This project is no longer supported and will be removed on October 29, 2010

Updated Wiki: Home

CodePlexAdmin — Mon, 27 Sep 2010 23:47:56 GMT

!Important Note: This project is no longer supported and will be removed on October 29, 2010

Project Description
The Mobile Browser Definition File contains definitions for individual mobile devices and browsers. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.

This project provides a data file that when used with ASP.NET will detect the incoming mobile device and present you as the web developer with a set of 67 capabilities or properties describing the requesting device. These capabilities range from screen size to cookie support and provide all the information you need to adaptively render content for mobile phones and devices.

What is the Mobile Device Browser Definition File?
The Mobile Device Browser Definition File contains capability definitions for individual mobile devices and browsers. At run time, ASP.NET uses this .browser file, along with the information in the HTTP request header, to determine what type of device/browser has made the request and what the capabilities of that device are. This information is exposed to the developer through the Request.Browser property and allows them to tailor the presentation of their web page to suit the capabilities of the target device.

More Information
The format of the .browser file is XML and the schema is defined here: Browser Definition File Schema. The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the browserCaps element was used to define browser definitions in configuration files. Please note that you must have you must have Microsoft .NET Framework 2.0 Service Pack 2 installed to use this .browser file. See requirements...

Final Release Announcement 15-July-2010
Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th July 2010 and the final release on the 24th August 2010.
We would like to thank everyone who used our product over the past year and a half. We would also like to thank everyone who contributed to the discussions and raised issues on our data.
Final Release Discussion

Links

Updated Wiki: Home

CodePlexAdmin — Mon, 27 Sep 2010 23:47:36 GMT

Important Note: This project is no longer supported and will be removed on October 29, 2010

Project Description
The Mobile Browser Definition File contains definitions for individual mobile devices and browsers. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.

This project provides a data file that when used with ASP.NET will detect the incoming mobile device and present you as the web developer with a set of 67 capabilities or properties describing the requesting device. These capabilities range from screen size to cookie support and provide all the information you need to adaptively render content for mobile phones and devices.

What is the Mobile Device Browser Definition File?
The Mobile Device Browser Definition File contains capability definitions for individual mobile devices and browsers. At run time, ASP.NET uses this .browser file, along with the information in the HTTP request header, to determine what type of device/browser has made the request and what the capabilities of that device are. This information is exposed to the developer through the Request.Browser property and allows them to tailor the presentation of their web page to suit the capabilities of the target device.

More Information
The format of the .browser file is XML and the schema is defined here: Browser Definition File Schema. The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the browserCaps element was used to define browser definitions in configuration files. Please note that you must have you must have Microsoft .NET Framework 2.0 Service Pack 2 installed to use this .browser file. See requirements...

Final Release Announcement 15-July-2010
Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th July 2010 and the final release on the 24th August 2010.
We would like to thank everyone who used our product over the past year and a half. We would also like to thank everyone who contributed to the discussions and raised issues on our data.
Final Release Discussion

Links

Updated Wiki: Home

aiburk — Thu, 15 Jul 2010 10:45:26 GMT

Updated Wiki: Home

aiburk — Thu, 15 Jul 2010 10:44:48 GMT

Project Description
The Mobile Browser Definition File contains definitions for individual mobile devices and browsers. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.

This project provides a data file that when used with ASP.NET will detect the incoming mobile device and present you as the web developer with a set of 67 capabilities or properties describing the requesting device. These capabilities range from screen size to cookie support and provide all the information you need to adaptively render content for mobile phones and devices.

What is the Mobile Device Browser Definition File?
The Mobile Device Browser Definition File contains capability definitions for individual mobile devices and browsers. At run time, ASP.NET uses this .browser file, along with the information in the HTTP request header, to determine what type of device/browser has made the request and what the capabilities of that device are. This information is exposed to the developer through the Request.Browser property and allows them to tailor the presentation of their web page to suit the capabilities of the target device.

More Information
The format of the .browser file is XML and the schema is defined here: Browser Definition File Schema. The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the browserCaps element was used to define browser definitions in configuration files. Please note that you must have you must have Microsoft .NET Framework 2.0 Service Pack 2 installed to use this .browser file. See requirements...

Final Release Announcement
Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th July 2010 and the final release on the 24th August 2010.
We would like to thank everyone who used our product over the past year and a half. We would also like to thank everyone who contributed to the discussions and raised issues on our data.
Final Release Discussion

Links

Updated Wiki: Home

aiburk — Thu, 15 Jul 2010 10:42:48 GMT

Project Description
The Mobile Browser Definition File contains definitions for individual mobile devices and browsers. At run time, ASP.NET uses the information in the request header to determine what type of device/browser has made the request.

This project provides a data file that when used with ASP.NET will detect the incoming mobile device and present you as the web developer with a set of 67 capabilities or properties describing the requesting device. These capabilities range from screen size to cookie support and provide all the information you need to adaptively render content for mobile phones and devices.

What is the Mobile Device Browser Definition File?
The Mobile Device Browser Definition File contains capability definitions for individual mobile devices and browsers. At run time, ASP.NET uses this .browser file, along with the information in the HTTP request header, to determine what type of device/browser has made the request and what the capabilities of that device are. This information is exposed to the developer through the Request.Browser property and allows them to tailor the presentation of their web page to suit the capabilities of the target device.

More Information
The format of the .browser file is XML and the schema is defined here: Browser Definition File Schema. The Browser Definition File was introduced in the .NET Framework version 2.0. In earlier versions of the .NET Framework, the browserCaps element was used to define browser definitions in configuration files. Please note that you must have you must have Microsoft .NET Framework 2.0 Service Pack 2 installed to use this .browser file. See requirements...

Final Release Announcement
Due to the organizational restructuring of the team that developed and supported the Mobile Device Browser file, we will no longer have the resources to support and update this CodePlex project. The team will be providing two more releases – one on the 27th July 2010 and the final release on the 24th August 2010.
We would like to thank everyone who used our product over the past year and a half. We would also like to thank everyone who contributed to the discussions and raised issues on our data.

Links

New Comment on "Getting Started"

deipec — Tue, 06 Apr 2010 18:46:39 GMT

How can I treat iPhones like regular browsers when using this solution?

New Comment on "Getting Started"

harryhazza77 — Tue, 05 Jan 2010 16:30:24 GMT

I tried it without a sub folder and got a null reference exception when running the website. This was resolved by moving the file from App_Browsers to App_Browsers\Devices

New Comment on "Getting Started"

jensenbox — Sat, 02 Jan 2010 00:33:51 GMT

Does aspnet_regbrowsers.exe work with this file? if so, it sounds like a much better way to deploy instead of carrying around a 6MB config file in my app and SCM. Plus you update in one place for the entire server. Thoughts? http://msdn.microsoft.com/en-us/library/ms229858(VS.80).aspx

New Comment on "Capabilities"

suprduprmn — Fri, 04 Dec 2009 17:08:25 GMT

Gruger and burley325. I am sure you have moved on but just in case, you can use: bool.Parse(Request.Browser["SupportsBlah"]); and that can be tested. Little less code for you.

New Comment on "Capabilities"

michel — Thu, 08 Oct 2009 09:05:59 GMT

Another solution to testing a string value to be true is to create an extension method for this simple task. Or easier, just create a private/protected method Boolean IsTrue(String value) to use in a (base)class. Since this check may only be used in the presentation layer, the problem is very minimal. I'm very impressed that there is such a nice solution for mobile development in ASP .NET.

New Comment on "Getting Started"

METROmilwaukee — Thu, 13 Aug 2009 16:37:35 GMT

1.) Why bother using a subfolder for App_Browsers as suggested? 2.) Request.Browser.IsMobileDevice functions just fine as is but how does the Request object or other code we write know how to find, read and reference the XML files in the App_Browser/Device folder?

New Comment on "Capabilities"

Gruger — Wed, 15 Jul 2009 13:47:49 GMT

Is it working fine for you?

New Comment on "Capabilities"

burley325 — Wed, 15 Jul 2009 04:16:20 GMT

Thanks gruger... I get that.... Don't know what to tell you about your other problem

New Comment on "Capabilities"

Gruger — Tue, 14 Jul 2009 22:20:40 GMT

I figured out that I do need to check the property as a String, like I asked above: (Request.Browser["SupportsEmbeddedFlashInWebPages"].ToLower() == "true"). Thats the way. I've got a weird problem now. I'm testing in my PC, running on Firefox last updated. I don't know why a parameter like "AcceptsImageJpeg" is returning false!! What should I do? The Request.Browser.Browser and the Request.Browser.IsMobileDevice are correct (Firefox and false, respectively). I dont know why I'm getting false for the bold attributes wich should be setted to true!

New Comment on "Capabilities"

burley325 — Tue, 14 Jul 2009 20:53:34 GMT

I am having a similar problem to Gruger. I am having trouble implementing these attributes.

New Comment on "capabilities"

Gruger — Tue, 14 Jul 2009 14:34:32 GMT

I'm trying to use the "bold" attributes, but they seem to be Strings instead of the type you put int the table above. Unlikely, its impossible to cast a string to boolean. Should I test (Request.Browser["SupportsEmbeddedFlashInWebPages"].ToLower() == "true"), for example? (using C#). It looks horrible... Could it be fixed to an Object, instead of a String?

Updated Wiki: FAQ

jordanneill — Fri, 05 Jun 2009 16:17:07 GMT

FAQ

Why am I getting "Object reference not set to an instance of an object."?
How do I deploy the .browser file at the machine level?
I found an error in your data, how do I submit a bug?
I submitted a bug, when will it be fixed?
Why is the .browser file so large?
A new device has been released to the market, when will you add support for it?
Why does my application crash with “Parser Error Message: The 'parentID' attribute must be specified on the 'gateway' tag.”?

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 AppBrowsers folder and place the .browser file in there. E.G. \AppBrowsers\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 Aspnetregbrowsers.exe tool, available in the %SystemRoot%\Microsoft.NET\Framework\version folder, or programmatically cause recompilation by using the BrowserCapabilitiesCodeGenerator class. Read more...

Note: if you are adding this .browser file to the global directory you must 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 .browser. Please ensure that you have .NET Framework 2.0 Service Pack 2 installed on your machine (see Requirements). 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.