Ofer,

You bring up a point that is not unique to flash.  There have been several discussions regarding where module files can/should be stored.  Usually, this question is regarding images, but a file is a file, right?

I think this thread has a good explaination with a couple options.

The short of it is your module is stored in /desktopmodules/[modulename].  It doesn't matter what the url is, that's where the module is coming from.  You can choose to store your flash files there, you can put them in /portals/[portalid]/flash, you can put them anywhere you want.  How you reference is just like any other application.  You should reference the physical location of the file, not what the url is representing.

As hooligannes pointed out, DNN is just another asp.net app.  Granted, it's a complex app, but an app none the less.  If you think about how you would go about writing pages from scratch, you would create your aspx page (old way) or master page (new way) and add your content as a user control.  DNN uses the same methodology.  The aspx part of the page is your root/default page.  All content is modules, which are ascx user controls.  The same rules apply either way.

The "magic" you refer to is just url rewriting.  This is a practice common across most sites these days.  DNN uses friendly urls to help the site with search engines and (imho) just make things look nicer.  Obviously, when you create a url path on the fly, you can not expect to be able to store files in that same location.  It's not a physical location, which is your only requirement for where you do store files.  The url rewriting process is pretty well documented, if you want to understand how that works.  Personally, I don't feel the need to know how it works, I just need to know what is going to happen.  The choice is yours. (See DotNetNuke Friendly Urls.pdf in the Documentation download)

Lastly, don't get discouraged.  Being good at DNN development takes time.  There is a learning curve, but once you really get it, you'll find ways to do anything you want using this great framework.  I also reiterate what was said earlier about helping others.  When the lightbulb goes off in your head (and it will), don't forget these forums exist.  A place to post problems does no one any good unless there are people there who post solutions.  When you're capable (and again, you will be), come back and help out.

Here is how I got it to work.

<div id="comercial">    
    <!--[if !IE]> -->
    <object type="application/x-shockwave-flash" data="mini_commercial.swf" width="114" height="81">
    <!-- <![endif]-->
   
    <!--[if IE]>
    <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="114" height="81"
     codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,19,0">
     <param name="movie" value="mini_commercial.swf" />
    <!--><!---->
     <param name="loop" value="true" />
     <param name="menu" value="false" />
     <param name="quality" value="high" />
     <p>This is <strong>alternative</strong> content.</p>
    </object>
    <!-- <![endif]-->
</div>

It works for both IE and FireFox.

John