Predicting how users connect RSS

• • Reply
  

  SKT_01

  Participant

  1930 Points

  435 Posts

  Re: Predicting how users connect

  Mar 14, 2009 03:30 PM|LINK

  billy_111

  Sorry i dont like altering the web.config file as it has caused me many problems before. Can you please advise me where the code you suggested should go? My web.config is below:-

  <?xml version="1.0"?><!--

  Note: As an alternative to hand editing this file you can use the

  web admin tool to configure settings for your application. Use

  the Website->Asp.Net Configuration option in Visual Studio.

  A full list of settings and comments can be found in

  machine.config.comments usually located in

  \Windows\Microsoft.Net\Framework\v2.x\Config

  -->

  <configuration>

  <configSections>

  <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

  <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

  <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

  <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

  <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>

  <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

  <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

  <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

  </sectionGroup>

  </sectionGroup>

  </sectionGroup>

  </configSections>

  <appSettings/>

  <connectionStrings/>

  <system.web>

  <customErrors mode="Off"/>

  <!--

  Set compilation debug="true" to insert debugging

  symbols into the compiled page. Because this

  affects performance, set this value to true only

  during development.

  -->

  <compilation debug="true">

  <assemblies>

  <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

  <add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  <add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

  <add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

  </assemblies>

  </compilation>

  <!--

  The <authentication> section enables configuration

  of the security authentication mode used by

  ASP.NET to identify an incoming user.

  --> <authentication mode="Windows"/>

  <!--

  The <customErrors> section enables configuration

  of what to do if/when an unhandled error occurs

  during the execution of a request. Specifically,

  it enables developers to configure html error pages

  to be displayed in place of a error stack trace.

  <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

  <error statusCode="403" redirect="NoAccess.htm" />

  <error statusCode="404" redirect="FileNotFound.htm" />

  </customErrors>

  -->

  <!-- Mobile devices -->

  <browserCaps>

  <filter>

  <case match="Series60/(?'version'\d+\.\d+)">
                      browser = "S60"
                      version = ${version}
                      IsMobileDevice = true

  </case>
   </filter>

  </browserCaps> 

   

  <pages>

  <controls>

  <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  <add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  </controls>

  </pages>

  <httpHandlers>

  <remove verb="*" path="*.asmx"/>

  <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>

  </httpHandlers>

  <httpModules>

  <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  </httpModules>

  </system.web>

  <system.codedom>

  <compilers>

  <compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">

  <providerOption name="CompilerVersion" value="v3.5"/>

  <providerOption name="WarnAsError" value="false"/>

  </compiler>

  <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">

  <providerOption name="CompilerVersion" value="v3.5"/>

  <providerOption name="OptionInfer" value="true"/>

  <providerOption name="WarnAsError" value="false"/>

  </compiler>

  </compilers>

  </system.codedom>

  <!--

  The system.webServer section is required for running ASP.NET AJAX under Internet

  Information Services 7.0. It is not necessary for previous version of IIS.

  -->

  <system.webServer>

  <validation validateIntegratedModeConfiguration="false"/>

  <modules>

  <remove name="ScriptModule"/>

  <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  </modules>

  <handlers>

  <remove name="WebServiceHandlerFactory-Integrated"/>

  <remove name="ScriptHandlerFactory"/>

  <remove name="ScriptHandlerFactoryAppServices"/>

  <remove name="ScriptResource"/>

  <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

  </handlers>

  </system.webServer>

  <runtime>

  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

  <dependentAssembly>

  <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>

  <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>

  </dependentAssembly>

  <dependentAssembly>

  <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>

  <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>

  </dependentAssembly>

  </assemblyBinding>

  </runtime>

  </configuration>

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 14, 2009 03:45 PM|LINK

  Thank you so much, that works perfectly. If i wanted to make this code work with ALL mobile devices would i be able to do this:-

  if (Request.Browser["IsMobileDevice"] == "true" || Request.Browser["Nokia"] == "true"

  || Request.Browser["Siemens"] == "true" || Request.Browser["Sony Ericsson"] == "true")

  {

  Response.Redirect("contact.aspx");

  }

  You said earliar:-

  then you have to define all mobile devices and to hire a developer team to do this.

  Would i not be able to define ALL mobile devices which have access to the Internet..?

• • Reply
  

  SKT_01

  Participant

  1930 Points

  435 Posts

  Re: Predicting how users connect

  Mar 14, 2009 03:59 PM|LINK

  billy_111

  Would i not be able to define ALL mobile devices which have access to the Internet..?

  Because there are thousands of different mobile devices it is a lot of work. The best way for my experience is to define only modern devices and browsers, e. g. iPhone, iPod touch, Windows Mobile 6.x, BlackBerry software version 4.6 and higher, T-Mobile G1 Android, Nokia Series 60, Opera Mobile, NetFront. Those phones are most used for mobile internet.

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 14, 2009 04:10 PM|LINK

  So if i wanted to define the main mobile devices used such as Nokia, Sony Ericsson, Samsung etc ... would i need to alter the code in the web.config file?

  How can i do this, as the code you suggeted before was beyond my knowledge..?

  Thanks Again

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 14, 2009 04:17 PM|LINK

  Sorry let me be abit more specific. according to stats the most mobile devices used are:-

  Motorola RAZR V3, LG VX8300,,Apple iPhone, Apple iPod Touch, LG, BlackBerry, Nokia, Windows Mobile, Opera Mobile & NetFront

  Would implementing this to work be a waste of time? I want to cover the mobile devices whihc are mostly used which is what you have suggested. I think its a much better idea. So do i need to alter anything in the web.config?

  What step do i take from here?

  Thanks for you help

  Appreciate it

• • Reply
  

  SKT_01

  Participant

  1930 Points

  435 Posts

  Re: Predicting how users connect

  Mar 14, 2009 04:43 PM|LINK

  Hello,

  you have to collect user agent strings and headers of the mobile devices. Like I have described it for your Nokia N95 you have to extract regular expressions to identify phones by user agent and define the device or browser in the Web.config or seperate Browser Definition Files. For every device a filter has to be added to the Web.config for example. This is not a waste of time but a lot of work.

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 15, 2009 04:39 AM|LINK

  Hey thanks,

  The code you suggested in the web.config, will it only work for Nokia N95 and not all Nokia mobile devices? I have found a whole load of user-agent headers shown below:-

  http://wiki.forum.nokia.com/index.php/User-Agent_headers_for_Nokia_devices

  N90: NokiaN90-1/3.0545.5.1 Series60/2.8 Profile/MIDP-2.0 Configuration/CLDC-1.1
  3200: Nokia3200/1.0 (5.29) Profile/MIDP-1.0 Configuration/CLDC-1.0 UP.Link/6.3.1.13.0
  N80: NokiaN80-3/1.0552.0.7Series60/3.0Profile/MIDP-2.0Configuration/CLDC-1.1
  7610: Nokia7610/2.0 (5.0509.0) SymbianOS/7.0s Series60/2.1 Profile/MIDP-2.0 Configuration/CLDC-1.0
  6600: Nokia6600/1.0 (5.27.0) SymbianOS/7.0s Series60/2.0 Profile/MIDP-2.0 Configuration/CLDC-1
  6680: Nokia6680/1.0 (4.04.07) SymbianOS/8.0 Series60/2.6 Profile/MIDP-2.0 Configuration/CLDC-1.1
  6230: Nokia6230/2.0+(04.43)+Profile/MIDP-2.0+Configuration/CLDC-1.1+UP.Link/6.3.0.0.0
  6630: Nokia6630/1.0 (2.3.129) SymbianOS/8.0 Series60/2.6 Profile/MIDP-2.0 Configuration/CLDC-1.1
  7600: Nokia7600/2.0 (03.01) Profile/MIDP-1.0 Configuration/CLDC-1.0 (Google WAP Proxy/1.0)
  N-GAGE: NokiaN-Gage/1.0 SymbianOS/6.1 Series60/1.2 Profile/MIDP-1.0 Configuration/CLDC-1.0
  5140: Nokia5140/2.0 (3.10) Profile/MIDP-2.0 Configuration/CLDC-1.1
  3519i: Nokia3510i/1.0 (04.44) Profile/MIDP-1.0 Configuration/CLDC-1.0
  7250i: Nokia7250i/1.0 (3.22) Profile/MIDP-1.0 Configuration/CLDC-1.0
  7250: Nokia7250/1.0 (3.14) Profile/MIDP-1.0 Configuration/CLDC-1.0
  6800: Nokia6800/2.0 (4.17) Profile/MIDP-1.0 Configuration/CLDC-1.0 UP.Link/5.1.2.9
  3650: Nokia3650/1.0 SymbianOS/6.1 Series60/1.2 Profile/MIDP-1.0 Configuration/CLDC-1.0
  8310: Nokia8310/1.0 (05.11) UP.Link/6.5.0.0.06.5.0.0.06.5.0.0.06.5.0.0.0

  If i put these in the web.config, will thw above mobile devices be covered?

  Sorry for all the 21 questions

• • Reply
  

  SKT_01

  Participant

  1930 Points

  435 Posts

  Re: Predicting how users connect

  Mar 20, 2009 12:21 PM|LINK

  Hello again,

  Microsoft has published a new Mobile Device Browser File that might be helpful for you.