macromedia flash flash remoting: Is there anybody worked Flash Remoting on ASP.NET version 2.0 (beta2)?

If so can you post a sample "hello world" sample.

Thanks a TON in Advance!!!!

Flash remoting under ASP.NET 2.0 sort of works. The simple hello world example
when calling a .aspx file works. Be careful under 2.0 that you have the
web.config permissions set properly. One of the default settings for primary
config file is
users deny = "?", I had to change this to users allow="*" in order for the
example code to be working. Also, be sure that the tracing options are
disabled since they appear to interfere.

That was the easy part. The reason I'm in the forum is to find out if anyone
has used the more complex FlashGateway.IO.ASObject call. Under .Net 2.0 when
flash.databind() is call (the flash.datasource = zzz completes) the system
throws an exception with the error message=' A value of type
'FlashGateway.IO.ASObject' cannot be serialized. '

Once I get this done then it is on to ?wsdl calls!!
Good luck. Hope this helps a little.

:-)

Thanks for your reply.

Can you post the sample code? or email to me srinin@gmail.com? Since there is
no DLL file in ASP.NET 2.0 who did you manage to read the a.aspx from flash?

I am also trying to pass my custom object from asp.net 2.0 / c# to flash which
is not working...

If you find anything please let me know, Thanks again

No problem. The sample code I used was part of the Flashremoting for .NET.
when you install the code it will create a directory under your default web
site called Flash remoting. there are two important files.
~/bin/flashgateway.dll and ~/gateway.aspx which is a dummy file to set up the
connection. You will also need define the flashgateway in the <httpmodule>
section of your web.config file.

All of the above is part of the PDF file that comes with the Flashremoting.NET
package.

let me know if this helps.

-m

mzadig, did you get this to work? I have the same problem, I get a "value of
type 'FlashGateway.IO.ASObject' cannot be serialized" error when I try to
return an aso object to Flash. I haven't gotten a simple hello world web
service to work either...

Regards,
- Bjarki

:camera;is there anybody who has the component of flashremoting for .net? I
have try many times to download from the www.macromedia.com, but everytime is
not successful. I beg for your email to me. and my email address is
lisacls_1@163.com! or tell me the address to download it! thanks firstly!

Thnx for yout response, but the problem is that i am already a customer and i
really believe that mm should solve this problem. I cant really understand why
they are not giving the appropriate support for a product that costs a lot of
money. Innovation in one part and leaving others not working at all does not
seems to me very professional. Or at least they should give us more information
so we know if we should continue with another software house. Anyway i will
look a bit deeper and if i find anything interesting i will post it here.

finCosmos,

I decided to check out WebOrb instead:
http://www.themidnightcoders.com/doc20/introduction/provsstd.htm
They also have way better documentation and tutorials and they support .net
framework 2.0 For me it was an easy choise...

Sorry that I didn't reply earlier.

I have been able to get Flash remoting working under .NET 2.0 but not
completely. I had to create a proxy service that operates through a special
purpose .aspx page instead of calling the flash remoting service dll.

The problem is that the .dll that you get with flash is only for .NET 1.x.
Macromedia indicated to me that they (at the time June) weren't supporting the
beta version. I didn't find this particularly unreasonable, though somewhat
annoying, since it is very difficult for a commercial supplier to support code
in motion. The good news was that it really didn't matter since I had the
proxy code running and it actually gives me far more functionality and
flexibility. I built the code with the out of the box flash remoting action
script interfaces. The code I wrote did not take advantage of the standard
components connection set ups. I had to code AS 2.0 classes that
programatically manage the connections, the returns and the data structures. A
lot of work but once they are set as classes everything works very well and
with much more control and maintenance predictability than you get with the out
of the box component interfacing.



I expect that once MS launches .NET 2.0 an update to the mm .dll will be made
available.

One more reason to use the proxy approach is that your development environmet
is much more flexible. You don't have to compile your responding .NET classes.
The proxy approach allows you to modify the responding classes directly in the
VS Studio environment, build your site and access it from the flash client. VS
Studio handles the compliation and Flash simply interacts with the development
site through a service call. I found that I had much more flexibility
integrating with newll developed classes and functions if I used this approach
(which is also referred to as the facade technique ). If you use the dll. then
you have to go through additional steps to use the service (in the case of 1.x,
2.x will suffer the same constraints once the proper .dll is released) . This
information regarding facades and .dll connectiing can be found in some of the
flash .Net tutorials on the MM site.

Regards,

m