Two development methods
1, ordinary ASP.NET
The page content (WML / XHTML) is output directly through the background method. Turn Response.ContentType, for example: text / wap.vnd.Wml, Application / XHTML XML.
You can also output through the front page as you write ASP.
2, MMIT
WML (WAP1.2): Basically MMIT can meet all the requirements of WML. It is very convenient to develop and have strong adaptability. A few things to pay attention to:
No session / without cookie / close enableViewState and EnableSessionState. Dreamnets and interactive perspectives can ensure that users' session do not use the paging controls of .NET, write pagins (not lazy) to properly configure the description of the terminal attributes in Machine.config / Web.config. There are no reference documents, there are several phones that need special configuration. However, those attribute values are simple, generally can understand, and it is better to test. Mmit itself has some bugs, for example, there is a problem on some simulators or very old mobile phones, but there is no problem in the current market; redirect needs to be rewritten; about the processing of special characters, sometimes in WML / XHTML is compatible with problems, it needs to be handled in advance; the problem of newline characters. XHTML (WAP2.0): Basically MMIT can support WAP2.0, and there is no problem when completing some common page effects, and can be controlled by using CSS. You can also use a custom control to perform XHTML text insertion. Complex XHTML pages may be supported, and you need to use standard ASP.NET methods to complete.
