If you compile your code to a .NET Assembly (i.e. a .NET DLL file) and place
it in the Local Assembly Cache (LAC) of the Flash Remoting-enabled web
application, then you should be able to access the classes using the Flash
Remoting Components.
What version of Microsoft.NET are you using? Note that Flash Remoting MX for
.NET was released for Microsoft .NET 1.0.
In order for a web application to be "Flash Remoting" enabled, you have to
have the following configuration and files in your web application:
1. The flashgateway.dll must be in the LAC or "/bin" sub-directory of your
web application.
2. /Web.Config must contain an HttpModule entry for the gateway - this is
necessary to intercept AMF formatted HTTP POST requests from the Flash
Player (it must be Flash Player 6 or higher)...
<httpModules>
<add name="GatewayController"
type="FlashGateway.Controller.GatewayController,flashgateway" />
</httpModules>
3. A blank .aspx file, say gateway.aspx, in the root directory to use in the
gateway URL so that ASP.NET handles the AMF request rather than IIS
(remember, when ASP.NET is properly installed IIS will have the necessary
.NET specific extension mappings for the web application configuration,
To check this, look at the Properties for your Web Site in the Internet
Information Services MMC. Go to the Home Directory tab. Click on
Configuration. Ensure there are .NET specific ISAPI extensions listed, e.g.
.aspx will be mapped to something like
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
If this mapping is not there, it is likely that you re-installed IIS after
installing Microsoft.NET. To restore ASP.NET, run the IIS registration
utility, i.e. run this command (but with the path to your .NET Framework
installation obviously):
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
With ASP.NET properly installed, and with, say, a blank gateway.aspx
file in the web application directory, you set the gatewayUrl to "/mywebappl
ication/gateway.aspx"
4. If you want to run remoting from a machine other than localhost, you need
to have a valid serial key. This is typically done at installation time, but
after the fact I think you can manually add the serial number to the
/bin/frconfig.txt file.
# Flash Remoting MX for .NET - Configuration File
SN=
IP=
Log Level=Error
Log File Size=1048576
If you don't have a serial key and wish to use the gateway from one other
machine besides localhost, you can add the IP address to the IP property in
this file. I think you might need to restart the IIS Admin and WWWRoot
services in order for changes to this file to be picked up by the gateway.
hi Pete
Thanks for your reply :)
I have installed Visual Studio .net 2003. and i have flash remoteing locally
in my matchin.
and all things are configured as per your reply.
but i dont know how to connect to .net assembly file.
can u send me some links of examples.
so i can refer..
i am refuring "Tom Muck"'s Flash remoting MX the definitive guide.
i have 1 example in that book. but i am not clear with that.
so pls help me ASAP
Thanks & Regards
Suketu Vyas (HOTKETU)
Pete - 22 Oct 2004 22:28 GMT
The service name would be the fully qualified class name of the public class
you're trying to call from your assembly.
I remember in earlier versions of Visual Studio .NET that it would prepend a
default prefix to class namespaces by default... whether or not this could
be configured in the VS project settings back then, I'm not sure... but the
best way to work out the real name of your class is to examine the assembly
using the special ildasm.exe tool that comes in the Visual Studio.NET SDK.
If you open your assembly DLL with ildasm.exe, you should be able to explore
the classes based on their full namespaces. Ensure that the service name
that you're using in your ActionScript code matches this fully qualified
name exactly...
> hi Pete
> Thanks for your reply :)
[quoted text clipped - 14 lines]
>
> Suketu Vyas (HOTKETU)