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

Calling ASP.NET assemblies from Flash 159
In the ActionScript code, you specify the serviceName argument with a URL that produces
WSDL. The
getTemp function maps to the web service method of the same name. Here, zip
represents an input text field, and
tempDisplay represents a dynamic text field.
To see the web service proxy assembly (with the .dll extension) that Flash Remoting creates, look
in your local assembly cache for a DLL with the same name as the web service. For the
Temperature web service, look for a DLL named TemperatureService.dll.
Calling ASP.NET assemblies from Flash
Using Flash Remoting, you can invoke .NET assembly files (with the .dll extension) from Flash.
In your ActionScript code, you use the fully qualified assembly or class file name in the
serviceName argument, and for the service function name, you use an assembly or class method
name. On the server, you must place your DLL and class files in the local assembly cache.
Calling assemblies from Flash
In the class file, you specify the
using directive to reference the Flash Remoting assembly
namespace FlashGateway.IO, as the following C# example shows:
using System;
using FlashGateway.IO;
namespace FlashRemoting.EchoTests
{
public class EchoClass
{
public EchoClass()
{
///Public constructor... initialize any member fields here if need be.
}
public string echoString(string s)
{
return s;
}
}
}
In the ActionScript code, you use the namespace and public class name defined in the class file, as
the following example shows:
import mx.remoting.Service;
import mx.remoting.PendingCall;
import mx.rpc.RelayResponder;
import mx.rpc.FaultEvent;
import mx.rpc.ResultEvent;
var classService:Service = new Service(
"http://localhost/myASPApp/default.aspx",
null,
"FlashRemoting.EchoTests.EchoClass",
null,
null);
var pc:PendingCall = classService.echoString(input.text);
pc.responder = new RelayResponder(this, "echoString_Result",