| Groups | Blog | Home |
asp.net mobile : several mobile asp.net issues
[this is a repost of my message posted originally to microsoft.public.dotnet.framework.aspnet two weeks ago. I got no answers but then I've found this group specific to mobile asp.net] I've just started to dig into mobile ASP.NET and I'd really wish to clarify few things. I have the experience with ASP.NET and I'd like to add a mobile support for my ASP.NET portal. Please excuse me if you will find some questions obvious. 1) Some tutorials mention something called Microsoft Mobile Internet Toolkit to be installed over .NET Framework 1.0. Is this Toolkit required when using ..NET Framework 1.1? At this moment my research indicate that MMIT is an integral part of .NET 1.1 and DOES NOT to be installed. Can anyone confirm that? 2) [related to 1.] What about so called "Updates" to MMIT? [the last update is number 4] Should I download and run the update package in the host machine? If yes then is this Update a part of .NET 1.1 SP 1? 3) http://www.asp.net/mobile/testeddevices.aspx?tabindex=6 lists several mobile phones that are compatible with mobile ASP.NET. What does it mean to "be compatible"? I need a clarification because I've tested my Noki a 3410 (it is NOT on the list) and it works with my test ASP.NET page! Does it mean that the list is incomplete? It is possible that much more mobile phones can read mobile ASP.NET pages? 4) After I'd noticed that the simple test page [http://dziennik.vulcan.pl/test.aspx, source provided at the end of this message] works with N3410, I've started to test other mobile phones. To my surprize, the test page does not work with Siemens ME45 (and two other Siemen ses). I've started to dig into that issue and tested my page with emulators from www.gelon.net. The test page works with most of emulators but, indeed, it does not work with Siemenses). However, the emulators says (you can see it by yourself) that "No WML page found. It's probably a HTML file..." and further "The page at http://dziennik.vulcan.pl/test.aspx is not a WML page! It's a ordinary HTML page. We know this because the server responded with the content type text/html when we made a request for http://dziennik.vulcan.pl/test.aspx This would been OK if it was a HTML page we where looking for, but it's not. What we want is a WML page." This is a big concern to me. Does it mean that the mobile ASP.NET does not produce WML page to a mobile device? Most tutorials claim that it does! Or does it mean that Siemens has a faulty or incompatible WML processor? Can I address this issue somehow and fix the page to be compatible with this particular browser or is it impossible? 5) what is the purpose of this <deviceFilters> section in web.config file? why it is important to define filters? Is it to block some mobiles from accessing pages or rather to enable some mobiles to access the page? 6) is it ok to have a non-mobile and a mobile application in the same directory with one web.config? if not then what is the best strategy to separate these two and still be able to use the same web directory for both non-mobile and mobile application? big thanks for the clarification of at least some of these issues regards, Wiktor Zychla // source ot the test page <%@ Page Inherits="System.Web.UI.MobileControls.MobilePage" %> <%@ Register TagPrefix="Mobile" Namespace="System.Web.UI.MobileControls" Assembly="System.Web.Mobile" %> <meta content="charset=utf-8"> <body Xmlns:mobile="http://schemas.microsoft.com/Mobile/WebForm"> <Mobile:Form runat="server"> - Ten o gasce Balbince?<br> - Alez Wodzu co Wodz!<br> - To ja przepraszam<br> <Mobile:TextBox runat="server">tu tekst</Mobile:TextBox> </Mobile:Form> </body>
Hi,
In Framework 1.1 it is a part of framework, but you still have to get all the updates (it updates some file in CONFIG directory of your ASP.Net engine plus adds Mobile Adapters DLL. "To be compatible" is probably to match a specification. You have to specify your mobile device in order ASP.Net render properly the controls. at asp.net you can create a profile. Profile can be HTML, XHTML or WML. If a device doesn't work properly, try to make specification (at the site asp.net, look at Mobile tab). [4] - the server responds (renders) response according to device specifications. Keep that in mind. "diveceFilters" allow you to create simple (compare) test filters in order to use in DeviceSpecific (a control you'll find quiet usefull when working with device specific content). You can also create CODED filters. [6] We do it, same root directory for WEB and WAP, sharing same Global.aspx, web.config and default.aspx start page, you can check on browser type and decide what you do further. This way both (web and wap) parts of application share the same logic (business logic, DB layer, etc). Hope it helped :) Sean -- With the best wishes, Sean Feldman [quoted text, click to view] "Wiktor Zychla" <user@nospam.com.eu> wrote in message news:uMosc2X8EHA.2608@TK2MSFTNGP10.phx.gbl... > Hi there, > > [this is a repost of my message posted originally to > microsoft.public.dotnet.framework.aspnet two weeks ago. I got no answers > but then I've found this group specific to mobile asp.net] > > I've just started to dig into mobile ASP.NET and I'd really wish to > clarify few things. I have the experience with ASP.NET and I'd like to add > a mobile support for my ASP.NET portal. > > Please excuse me if you will find some questions obvious. > > 1) Some tutorials mention something called Microsoft Mobile Internet > Toolkit > to be installed over .NET Framework 1.0. Is this Toolkit required when > using > .NET Framework 1.1? At this moment my research indicate that MMIT is an > integral part of .NET 1.1 and DOES NOT to be installed. Can anyone confirm > that? > > 2) [related to 1.] What about so called "Updates" to MMIT? [the last > update > is number 4] Should I download and run the update package in the host > machine? If yes then is this Update a part of .NET 1.1 SP 1? > > 3) http://www.asp.net/mobile/testeddevices.aspx?tabindex=6 lists several > mobile phones that are compatible with mobile ASP.NET. What does it mean > to > "be compatible"? I need a clarification because I've tested my Noki a 3410 > (it is NOT on the list) and it works with my test ASP.NET page! Does it > mean > that the list is incomplete? It is possible that much more mobile phones > can > read mobile ASP.NET pages? > > 4) After I'd noticed that the simple test page > [http://dziennik.vulcan.pl/test.aspx, source provided at the end of this > message] works with N3410, I've started to test other mobile phones. To my > surprize, the test page does not work with Siemens ME45 (and two other > Siemen ses). I've started to dig into that issue and tested my page with > emulators from www.gelon.net. The test page works > with most of emulators but, indeed, it does not work with Siemenses). > However, the emulators says (you can see it by yourself) that > > "No WML page found. It's probably a HTML file..." > > and further > > "The page at http://dziennik.vulcan.pl/test.aspx is not a WML page! It's a > ordinary HTML page. > We know this because the server responded with the content type text/html > when we made a request for http://dziennik.vulcan.pl/test.aspx > This would been OK if it was a HTML page we where looking for, but it's > not. > What we want is a WML page." > > This is a big concern to me. Does it mean that the mobile ASP.NET does not > produce WML page to a mobile device? Most tutorials claim that it does! Or > does it mean that Siemens has a faulty or incompatible WML processor? Can > I > address this issue somehow and fix the page to be compatible with this > particular browser or is it impossible? > > 5) what is the purpose of this <deviceFilters> section in web.config file? > why it is important to define filters? Is it to block some mobiles from > accessing pages or rather to enable some mobiles to access the page? > > 6) is it ok to have a non-mobile and a mobile application in the same > directory with one web.config? if not then what is the best strategy to > separate these two and still be able to use the same web directory for > both non-mobile and mobile application? > > big thanks for the clarification of at least some of these issues > > regards, > Wiktor Zychla > > // source ot the test page > <%@ Page Inherits="System.Web.UI.MobileControls.MobilePage" %> > <%@ Register TagPrefix="Mobile" Namespace="System.Web.UI.MobileControls" > Assembly="System.Web.Mobile" %> > <meta content="charset=utf-8"> > <body Xmlns:mobile="http://schemas.microsoft.com/Mobile/WebForm"> > <Mobile:Form runat="server"> > - Ten o gasce Balbince?<br> > - Alez Wodzu co Wodz!<br> > - To ja przepraszam<br> > <Mobile:TextBox runat="server">tu tekst</Mobile:TextBox> > </Mobile:Form> > </body> > > >
Don't see what you're looking for? Try a search.
|
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
February 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |