Communication between FLASH and ASP.NET

Question

0.00/5 (No votes)

See more:

I am trying to understand of going back and forth between SWF pages and ASPX pages. What are things that slow them down or make them faster and smoother? Where is the best place to put a progress bar, in the SWF page? or ASP.NET page? Anything else I should be careful of? Any answers or pointing me to a good article would greatful. Thanks! :)

Posted 15-Feb-13 22:36pm

GreenKhan

Add a Solution

Comments

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) 16-Feb-13 4:39am

I also need the answer.
Somebody will help us.

I can find the article links, but I need to get the correct one, following which I can start from scratch and communicate between Flash and Asp.Net.

GreenKhan 16-Feb-13 4:43am

I dont have a problem communicating with them. I can pass VARs etc and load them. Id just like to know how they work more. Like when a button (to LOAD and GO to SWF page) is clicked in the ASP.NET, what happens, is it spending more time in the current ASP.NET page before it goes? Or does it go directly and start doing stuff in the SWF page? Cause after a button click it seems to take some time to load sometimes. What is it loading on going and coming between pages, etc.

Muthuraja Irullandi 16-Feb-13 12:36pm

Hi,
As per my understanding, if the button click event happens in the asp.net page, then it will again reload the page, including the swf. So this might take some time.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)