update: t is de wap versie ofzowiets van messenger:
japanse versie effe vertaald
Lastly, the cord/code of the Mobile Internet Toolkit edition MSN Sender will be explained simply. The following list is called when " the transmission " button is clicked, it is event * handler, (Command1_Click method). Here MSN Messenger Web service is called in the same way as the last time, but as the Web application edition MSN Sender it probably will understand that completely it is the same cord/code.
Private void Command1_Click (object sender, System.EventArgs E) {
/ Making use of Web service, message is transmitted
Messenger m = new Messenger ();
Bool result = m.AnonymousSendMessageNonSoap (textRcpt.Text and textMessage.Text);
/ According to the transmission result, indicatory form it changes
If (result) {
ActiveForm = Form2;
} Else {
ActiveForm = Form3;
}
}
It calls Web service and transmits message method
MSN Messenger Web service is called in the same way as the last time, but completely it is the same cord/code as the Web application edition MSN Sender.
After calling Web service, on the basis of the bool value which displays the success or failure, active * form is changed the Form2 (transmission success) the Form3 (the failure of transmission) to. To the ActiveForm property it executes this by the fact that form object is substituted. Furthermore, the link which " returns " being arranged in the Form2 and the Form3, when this is clicked, it has reached the point where it returns to the Form1. As for this, because " the #Form1 " is set to the navigatecUrl property of Link control, is possible the fact that active * form is changed to the Form1 not to depend on event handler.
Build procedure of the MSN Sender is shown next.
For Mobile Web application saying, because the actual condition utilizes the control which is added with the Mobile Internet Toolkit extremely the general Web application which only it is, build procedure of the Mobile Internet Toolkit edition MSN Sender almost is not different from the last time. Barely, 1 options are added just at the time of compiler starting.
1. Starting Internet * service * manager, it draws up the hypothetical directory (example: C: It sets the \MSNSender as the hypothetical directory MSNSender)
2. Starting command * prompt, the c: Command below is executed with the \MSNSender, the Messenger.cs is drawn up.
Wsdl /n:MSNSender
Http: //65.116.26.9/messengerwebsrv/messengerservice.asmx
3. C: Draws up the source * file below in the \MSNSender (download of the source file this way: Mitmsnsender.zip (data compressed file) ).
AssemblyInfo.cs
Global.asax
Global.asax.cs
SenderForm.aspx
SenderForm.aspx.cs
Web.config
4. Directory c: The \MSNSender\bin is drawn up.
5. C: It executes the command below with the \MSNSender, compiles (the c: The \MSNSender\bin\MSNSender.dll is drawn up). This time unlike the last time, appointing " the /r:System.Web.Mobile.dll ", it is necessary to indicate the link to the Mobile * server * control * library.
Csc /r:System.Web.Mobile.dll /t:library /out:bin\MSNSender.dll
AssemblyInfo.cs Global.asax.cs Messenger.cs SenderForm.aspx.cs
When job above is finished, the http: It reaches the point where the Web page of the MSNSender is opened from the //127.0.0.1/MSNSender/SenderForm.aspx. Because with the digital advantage and the IWebMethodc.net which is managed jointly with the @IT, the last time in the same way, also the latest MSNSender is open, we want the person who would like to try trying accessing this way. This URL has become as follows, (even from the IE access yes).
:strip_icc():strip_exif()/u/3163/smallcat.jpg?f=community)
/u/20796/crop64ea633835d95_cropped.png?f=community)
:strip_icc():strip_exif()/u/34345/crop604df19f86683.jpg?f=community)
:strip_exif()/u/3981/icon.gif?f=community){kind=icon}
/u/30431/crop55f8174d06676_cropped.png?f=community)
MESSENGER!:strip_exif()/u/3319/GoT-Logo%2520-%2520Webicon.gif?f=community)
/u/48908/avatar.JPG?f=community){kind=avatar}