You want to configure Flash Remoting for .NET.
Add the flashgateway.dll file
to the .NET web
application’s bin directory and
create a blank gateway.aspx file in the web
application’s root directory. The file and folder
permissions must be set to allow access to .NET web services. For
example, web services won’t work if the ASP.NET user
doesn’t have permission to
support all Flash Remoting features, install the entire .NET SDK on
the server, and not just the limited .NET Framework.
Flash Remoting for .NET allows Flash clients to communicate with Windows .NET applications. The Flash Remoting for .NET gateway is sold separately by Macromedia (see http://www.macromedia.com/software/flashremoting/productinfo/versions_pricing). You must download and install either the trial version or full version before proceeding.
To use Flash Remoting for .NET, two things must be properly configured on the server: the Flash Remoting assembly (flashgateway.dll), which implements Flash Remoting support on the server, and an ASPX page, which is used as the Flash Remoting gateway. If you have installed Flash Remoting for .NET, the default installation creates a flashremoting directory within the IIS web root (usually C:\Inetput\wwwroot). The flashgateway.dll assembly file can be found within the bin directory of that directory, and you should copy it to the bin directory of your own .NET web application. Additionally, you ...