Saturday, September 11, 2010
Forum   
 
ForumForumProductsProductsMobile Toolkit ...Mobile Toolkit ...No mobile controls device configuration was registered for the requesting deviceNo mobile controls device configuration was registered for the requesting device
Previous Previous
 
Next Next
New Post
 7/27/2010 3:03 PM
 
amaresh_jois
No Ranking

Joined: 1/1/2010
Posts: 33

Hello psynergy42,

If you are not using all the sections under configsections, you can modify the config section to contain only fiftyOne section group as shown,
<configSections>
<sectionGroupname="fiftyOne">
<sectionname="log"type="FiftyOne.Foundation.Mobile.Configuration.LogSection, FiftyOne.Foundation"requirePermission="false"allowDefinition="Everywhere"restartOnExternalChanges="false"allowExeDefinition="MachineToApplication"/>
<sectionname="redirect"type="FiftyOne.Foundation.Mobile.Configuration.RedirectSection, FiftyOne.Foundation"requirePermission="false"allowDefinition="Everywhere"restartOnExternalChanges="false"allowExeDefinition="MachineToApplication"/>
<sectionname="wurfl"type="FiftyOne.Foundation.Mobile.Detection.Wurfl.Configuration.WurflSection, FiftyOne.Foundation"requirePermission="false"allowDefinition="Everywhere"restartOnExternalChanges="false"allowExeDefinition="MachineToApplication"/>
</sectionGroup>
</configSections>
Also, please change the wurfl section to contain all the attributes
<wurfl wurflFilePath="~/App_Data/wurfl.xml.gz"
newDevicesURL="http://devices.51degrees.mobi/New.ashx"
newDeviceDetail="maximum"
useActualDeviceRoot="false">
Can you please try using the Default.aspx file which is under Mobile folder as provided in Detector sample? If you do that, you need to change your redirection section as shown below.
Please do not delete any attribute in this section.
<redirect
firstRequestOnly="true"
mobileHomePageUrl="~/Mobile/Default.aspx"
timeout="20"devicesFile="~/App_Data/Devices.dat"mobilePagesRegex="~/Mobile/"/>
Let me know if this helps!
- Thank You
- Amaresh
New Post
 7/27/2010 3:36 PM
 
james
10th Level Poster

Joined: 1/23/2009
Posts: 117

This thread from ASP.NET suggests this exception could be caused by a browser caps element in the web.config. Could it be possible you have a web.config configuration in a parent web site that contains a browser caps element? This can happen if the detector example is installed as a virtual web application.

Alternatively if you reverse the changes to your web.config does the exception stop appearing?

James

New Post
 7/28/2010 8:03 AM
 
psynergy42
No Ranking

Joined: 7/25/2010
Posts: 5

I checked the parent webconfig for a browser caps element and created a seperate web site instead of a virtual web site. None of these had any effect. Correct me if I am wrong in assuming that the wfurl patch file is to allow regular browser to render the mobile controls on the redirected mobile page? Or is this exclusive to mobile devices alone?

New Post
 7/28/2010 8:24 AM
 
amaresh_jois
No Ranking

Joined: 1/1/2010
Posts: 33

Hello,

WURFL is a database file which contains info of almost all mobile devices. Please visit http://wurfl.sourceforge.net/index.php for more info
We have provided the web_browsers_patch.xml to quickly add any device info which is not available in WURFL database file.

I suggest you to host and run the detector sample on your emulator/ mobile which provides you a prototype for the mobile websites. From there you can build on your code.
BTW, can I know what is the end usage of your Mobile website?

Let me know if you need any more info!

- Thank You
- Amaresh

New Post
 7/28/2010 9:52 PM
 
james
10th Level Poster

Joined: 1/23/2009
Posts: 117

So the same exception occurred with a separate web site on the same machine?

As we've not heard of this exception before and it seems so closely related to browser caps is there anyway the default ASP.NET configuration files could have been changed to somehow alter the browser caps settings? Can you provide more information about the OS, IIS version, etc?

Regarding the Wurfl patch file they enable other devices mobile/non-mobile to be specified without requiring the main wurfl file to be changed. Unless you're really familiar with Wurfl they should probably be avoided and stick with our default ones.

James

 Page 2 of 5
Previous123...5Next 
Previous Previous
 
Next Next
ForumForumProductsProductsMobile Toolkit ...Mobile Toolkit ...No mobile controls device configuration was registered for the requesting deviceNo mobile controls device configuration was registered for the requesting device
Privacy Statement  |  Terms Of Use
Copyright 2009 - 2010 by 51 Degrees Mobile Experts Limited