several mobile asp.net issues


W

Wiktor Zychla

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

Advertisements

S

Sean Feldman

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
Wiktor Zychla said:
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>
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top