Incorporating Flash into an .aspx page

[cgdev1]

Hi Folks,

I'm somewhat a newbie to .Net (2.0) and even newer to Flash. I'm
trying to incorporate a flash (.swf) file into my application.

The code* below works in a .htm page (added to my project by using 'add
new item' and pasting the code in it). However, the same code does not
work in an .aspx page (the page does not throw any errors, but nothing
happens aside from a border and a tool tip that says to click to
activate). I also tried changing the path to "~/PhotoChange.swf".

(* I generated this code using Flash MX 2004 by 'publishing' as an html
file, then right clicking the resulting file and viewing the source)

Any ideas?

Thanks

<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000"
codebase="http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,0,0"
width="550" height="400" id="PhotoChange" align="middle">
<param name="allowScriptAccess" value="sameDomain" />
<param name="movie" value="PhotoChange.swf" />
<param name="quality" value="high" />
<param name="bgcolor" value="#ffffff" />
<embed src="PhotoChange.swf" quality="high" bgcolor="#ffffff"
width="550" height="400" name="PhotoChange" align="middle"
allowScriptAccess="sameDomain" type="application/x-shockwave-flash"
pluginspage="http://www.macromedia.com/go/getflashplayer" />
</object>

 

[Guest]

You could be suffering any of a number of ills.

Three suggestions:

a) test with FireFox: I'm not an evangelist, but it doesn't cache
(nonfunctional) versions of Flash instances nearly as aggressively as IE
does.
b) spend $10 and buy the epicFlashControl if you're working in VS.NET. The
control solves many issues such as the Eolas fix automatically, and will
eliminate most "dummy" errors.
c) if you're attempting any dynamic dataloading -- say, loads via LoadVars
or other objects for loading external assets -- get your page working OK
with a static movie first.

My experience is that ASP.NET isn't any easier or harder to place Flash with
than any other technology, and its server-side capabilities are a great fit
given Flash's "sandbox" security tendencies.

-KF

 

[Steve C. Orr [MCSD, MVP, CSM, ASP Insider]]

I agree that Flash is too hard in ASP.NET.
That's why I made this free control to encapsulate all the intricacies:
http://SteveOrr.net/articles/Flasher.aspx