User Guide
Table Of Contents
- Contents
- About Flash Remoting
- Getting Started
- Using Flash Remoting ActionScript
- Using the RemotingConnector component (Flash Professional only)
- Using Flash Remoting Data in ActionScript
- About Flash Remoting and data types
- Understanding Action Message Format
- Converting from ActionScript to application server data types
- Converting from application server data types to ActionScript
- ColdFusion to ActionScript data conversion issues
- About working with objects
- About working with RecordSet objects
- About working with XML
- The NetConnection Debugger
- Using Flash Remoting with ColdFusion MX
- Using Flash Remoting for Java
- About Flash Remoting for Java
- Calling Java classes or JavaBeans from ActionScript
- Calling Enterprise JavaBeans (EJBs) from Flash
- Calling servlets and JSPs from Flash
- Calling JMX MBeans from Flash (JRun only)
- Calling server-side ActionScript from Flash (JRun only)
- Handling function results in ActionScript
- Using Flash Remoting with JRun security
- Passing XML objects between Flash and Java
- Viewing Flash Remoting log entries
- Using Flash Remoting for Microsoft .NET
- Flash Remoting for Microsoft .NET
- Calling ASP.NET pages from Flash
- Making an ASP.NET page available to Flash Remoting
- Getting a reference to an ASPX-based service in ActionScript
- Invoking ASPX pages in ActionScript
- Using the Flash Remoting custom server control in ASPX pages
- Using the Flash Remoting namespace in code-behind files
- Using ASP.NET state management with Flash Remoting
- Using ASP.NET exception handling
- Using ADO.NET objects with Flash Remoting
- Displaying a RecordSet object in Flash with ActionScript
- Calling web services from Flash
- Calling ASP.NET assemblies from Flash
- Viewing Flash Remoting log entries
- Using NetServices and Connection Classes
- Index

148 Chapter 8: Using Flash Remoting for Microsoft .NET
function gotResourcesFault( fe:mx.rpc.FaultEvent ): Void {
trace( "error occurred"+ fe.fault.faultstring );
}
The gateway URL must reference an ASPX page inside the application directory. You should
use the gateway URL only during development in the Flash authoring environment. When
you deploy the Flash application, you should supply the gateway URL using a parameter in the
HTML that embeds the SWF file in the web page. For more information on supplying the
gateway URL in a web page, see “Specifying the gateway connection in a web page”
on page 38.
You must provide the fully qualified path to the directory that contains the page that you want
to invoke.
Invoking ASPX pages in ActionScript
After you have a reference to the ASPX page, you can use ActionScript functions to invoke it. For
example, the following ActionScript code invokes the ASPX page GetResources.aspx, assuming
that aspxService represents your reference to the directory that contains the ASPX page:
var pc:PendingCall = aspxService.GetResources();
The ASPX page's filename, GetResources.aspx, becomes the function name, GetResources().
This is the complete example:
import mx.remoting.Service;
import mx.remoting.PendingCall;
import mx.rpc.RelayResponder;
import mx.rpc.ResultEvent;
import mx.rpc.FaultEvent;
var aspxService:Service = new Service( "http://localhost/flashremoting/
gateway.aspx", null, "flashremoting.samples", null, null );
var pc:PendingCall = aspxService.GetResources();
pc.responder = new RelayResponder( this, "gotResources", "gotResourcesFault"
);
function gotResources( re:mx.rpc.ResultEvent ):Void {
trace( "got resources-"+ re.result );
}
function gotResourcesFault( fe:mx.rpc.FaultEvent ): Void {
trace( "error occurred"+ fe.fault.faultstring );
}