Predicting how users connect RSS

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Predicting how users connect

  Mar 14, 2009 03:31 AM|LINK

  Hey,

  I was wondering if you can help me on something i need to figure out. I have 2 websites, one is a main website, and the other is a mobile phone website, where users can connect using their mobile phones.

  However what i want to do is that if somebody tries to connect to the main website through their mobile phone it re-directs them to the mobile website as the CSS layout of the main website wil not suit users needs if they try to connect using a phone.? can this be done..?

  Much appreciated

  billy

  • Moved by mbanavige on Mar 14, 2009 03:45 AM
• • Reply
  

  IsToFix

  Participant

  837 Points

  133 Posts

  Re: Predicting how users connect

  Mar 14, 2009 05:35 AM|LINK

   You can determine if the browser is from mobile client by using HttpContext.Current.Request.Browser.IsMobileDevice now u need to handle the redirection very early so consider putting your logic in your main site globale.ascx Application_BeginRequest event handler. Do the check and if the it's mobile device make the redirection to your mobile website.

  Hope that helps
  

  Mark "answer" if my post helped you find the answer.
  "And say: My Lord increase me in knowledge."
  
  B/R

  Huthaifa Afanah

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 14, 2009 12:36 PM|LINK

  Hey,

  Thanks that was really helpful. I had a look around and found the following code:-

  if (Request.Browser["IsMobileDevice"] == "true")

  {

  Response.Redirect("default.aspx");

  }

  else

  {

  Response.Redirect("contact.aspx");

  }

   I have put this into the page load of my default page of the main website. As people connect to my main website it will redirect them to the mobile website. However this code seems to be connecting me to the contact page and not the default.aspx page..? If i connect to the website on my laptop it takes me to the contact.aspx page, and if i connect using my mobile device it does the same. How can i fix this?

  Thanks

   

• • Reply
  

  SKT_01

  Participant

  1930 Points

  435 Posts

  Re: Predicting how users connect

  Mar 14, 2009 02:36 PM|LINK

  Hello,

  which device are you using? Probably you have to define your phone as mobile device.

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 14, 2009 02:38 PM|LINK

  Thanks for replying. The phone i am using is Nokia n95, but i want the code to work with every mobile device, so how can i do this?

• • Reply
  

  IsToFix

  Participant

  837 Points

  133 Posts

  Re: Predicting how users connect

  Mar 14, 2009 02:51 PM|LINK

   Some mobile device does not introduce themselves as mobiles. Anyway check this link http://forums.asp.net/p/1024393/1392672.aspx
  

  Mark "answer" if my post helped you find the answer.
  "And say: My Lord increase me in knowledge."
  
  B/R

  Huthaifa Afanah

• • Reply
  

  SKT_01

  Participant

  1930 Points

  435 Posts

  Re: Predicting how users connect

  Mar 14, 2009 02:57 PM|LINK

  Hello,

  billy_111

  The phone i am using is Nokia n95 ..

   

  Paste the following code in the browserCaps section of the Web.config of your application.

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

   

  billy_111

  ... but i want the code to work with every mobile device, so how can i do this?

   

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

   

   

   

  • Marked as answer by billy_111 on Mar 14, 2009 03:47 PM
• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 14, 2009 03:08 PM|LINK

  Hey,

  I think i am getting somewhere. I am using the following code:-

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

  {

  Response.Redirect("contact.aspx");

  }

  When i connect via laptop it takes me to default.aspx which is fine but when i connect with the Nokia N95 it still takes me to default.aspx. So this means it does not recognize the mobile device..? Any ideas

  Thanks

• • Reply
  

  SKT_01

  Participant

  1930 Points

  435 Posts

  Re: Predicting how users connect

  Mar 14, 2009 03:12 PM|LINK

  Hello,

  I just wrote you how to define the Nokia N95.

• • Reply
  

  billy_111

  Member

  333 Points

  878 Posts

  Re: Predicting how users connect

  Mar 14, 2009 03:17 PM|LINK

  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>

  -->

  <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>