User Guide

Table Of Contents
Calling ASP.NET pages from Flash 151
...
}
}
The following VB.NET example performs the same operation:
Namespace Samples.ado
Public Class CustomerInfo
Inherits System.Web.UI.Page
Protected Flash As FlashGateway.Flash
After you establish the Flash Remoting namespace, you can manipulate the server control
properties in the
Page_Load method definition, as the following VB example shows:
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load{
dim message as string
message = "Hi "
if Flash.Params.Count > 0 then
message = message & Flash.Params(0).ToString() & " " &
Flash.Params(1).ToString()
end if
Flash.Result = message
End Sub
In the code, if the value of the Flash.Params.Count property is at least 1, two parameters passed
from Flash are appended to a string and returned to Flash.
Using ASP.NET state management with Flash Remoting
Flash Remoting supports ASP.NET cookie-based state management, which maintains a user
session using HTTP header information. Flash Remoting maintains the session ID automatically
by passing the session ID to the server in each subsequent service function request. To access
session variables in Flash applications using Flash Remoting, you can code a service function that
returns session variables using the
ResultEvent class.
Note: Flash Remoting does not support .NET cookieless state management.
Using the Flash Remoting custom control properties, you can access and set the values of session
variables. Session variables persist during a browser session from page to page. If you use Flash
Remoting to return session variables, Flash applications embedded in different pages can access a
common set of data.
To enable state management in an ASP.NET application, you use the
sessionState tag in the
config.web file, as the following example shows:
<configuration>
<sessionState
mode="inproc"
cookieless="false"
timeout="20"/>
</configuration>