You may be wondering what it means, and more importantly how to fix it. What appears to be the sole cause of this error is your versions not matching up between your Flex/AIR SDK and the AIR application descriptor file. This can happen after you update/reinstall Flash Builder, or the SDK folder manually.

The fix is pretty easy: Just open your AIR descriptor file(generally the only XML file in the project src folder) and change the xmlns to the current version of the SDK you are using(1.5.3 => 2.0 for instance). See screenshot below for an example(warning: it’s big):

1. (Re)start the Windows Installer service
   1. Right-click on Computer
   2. Click Manage
   3. Expand Services and Applications
   4. Select Services
   5. Scroll down to “Windows Installer”
   6. Right-click or double-click on it and make sure it is started and NOT disabled
2. Run “sfc /scannow” from a command prompt as Administrator
   1. Should see something like: windows resource protection found some corrupt files but was unable to fix them
      1. Check the log to see if the problem is a corrupt file such as “msi.dll”
         1. Do this by searching for “cannot repair”
      2. If that is the case you can restore this file from the Windows DVD by:
         1. Insert the Windows DVD in the drive, cancel the autorun if it pops up
         2. Open 7-zip and browse to “install.wim” in the DVD:\Sources folder (open it)
         3. Inside you will find numbered folders corresponding to the windows version, open yours:

            1=Home Basic

            2=Home Premium

            3=Professional

            4=Ultimate

         4. Browse to the folder for the version you have installed, and you can copy/extract the file(s) you need. In my case I needed “msi.dll” in the #\Windows\System32 folder
         5. Note that if you are restoring a sensitive file such as this that you have to take ownership of the original file to rename/remove it before you can restore this file from the DVD, and ideally set the restored file back to the original owner and permission.
         6. Also note that the “msi.dll” file is owned by “TrustedInstaller”, so if you are getting a security error you need to take ownership of the file to replace it and then restore TrustedInstaller as the owner. If you can’t find it when you “check” the name use “NT SERVICE\TrustedInstaller”
3. Restore an earlier restore point(not verified to work but try it..)
4. Run the repair option from the installer DVD
5. Reinstall Windows

Hope this helps someone.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" 
    layout="absolute"
    width="600" height="588"
    applicationComplete="start()">
    <mx:HDividedBox id="divBox" 
    	height="100%" width="99%"
    	liveDragging="true"
    	doubleClickEnabled="true">
          <mx:Canvas width="50%">
          		<mx:Text text="Some example text" />
          </mx:Canvas>
          <mx:Canvas width="50%">
          		<mx:Text text="Some example text" />
	      </mx:Canvas>
     </mx:HDividedBox>
     <mx:Script>
          <![CDATA[
               private function start():void {
                    divBox.getDividerAt(0).addEventListener(MouseEvent.DOUBLE_CLICK, handleDoubleClick);
               }
 
               private function handleDoubleClick(e:MouseEvent):void {
                    Alert.show('Event captured!');
               }
          ]]>
     </mx:Script>
</mx:Application>

The specific resolution was to enable liveDragging and add the event to the divider itself(most people try to set it on the doubleClick property of the DividerBox).

Hopefully this post will be helpful to some people out there with the same issue!

So, with that said the process is fairly simple. The following is a hypothetical example of a class you have imported into your application:

package com.example.scope
{
    private var myVar:String = 'This is NOT the value we're trying to get';
 
    public class scopeExample
    {
        public function scopeExample()
        {
            import mx.core.Application; // make "Application" available in the current scope
            trace(Application.application.myVar); // outputs the value of myVar in the main application
        }
    }
}

You could also use:

trace(parentDocument.myVar); // if the component is a child of the main application

I ran across a post on Holly Schinsky’s blog the other day that had good descriptions of the various scope keywords, and a few tips. All of which is good knowledge to possess, so check it out.

To run as administrator you have a couple of options.. if you’re running a home version of Vista, you might not have some of them:

1. Right-click on the Shortcut or game executable and click Run as Administrator
2. Right-click on the game executable and Click Properties->Compatibility->Check the “Run as Administrator” box, Apply
3. Right-click on the Shortcut, Click the “Shortcut” tab->Advanced, Check the “Run as Administrator” box, Apply

Now, with that said, none of these would work properly for me. The only solution I could find that would work is downloading this update from PunkBuster, adding my game, and hitting Update. Once updated the game ran fine without giving it extra privileges.

Good luck!

You can use them statically(without instantiating an object) like so:

trace(Keyboard.TAB); // 9

Namely:

1. Use “Release” build — by default the SWF is built with Debug mode and has debug & profiler code in it that your application doesn’t need.
2. Move your panels into modules(see movie)
3. Use the RSLs instead of compiling the Flex framework into your SWF

Using these suggestions has removed over 500K from my app.

The video shows you how to do all of these in Flex Builder.

Here is how you can perform the same optimizations in FlashDevelop:

Number 1 is fairly easy: Just find the only drop-down menu in the main interface, and change it from “Debug” to “Release”.

With number 2 you follow the same instructions, but you can get to the menu to add an item by right-clicking on your project in the “Project” pane of the right column, or by going to “File”->”New”.

Number 3 is slightly more complicated. First you need to get to your project’s properties menu, which you can do one of several ways. Here is a screenshot of going through the “Project” menu:

Then, click on the “Compiler Options” tab, and select the “Advanced Compiler Options” by clicking on it and clicking the “…” button. Then add the line “-static-rsls=false” to it as shown(or append it on a new line if you have other options set already).

Now, you have to copy the “framework_3.2.*.swf” and “framework_3.2.*.swz” files to the “bin” directory in your project, and upload them to your site when you upload your app. These contain the Flex framework that will be cached by the Flash Player when you run your app. They are located in “flex_sdk_3\frameworks\rsls” in the Flex 3 SDK folder. Note that whatever version of the SDK you compiled your app with is the version you have to use the RSLs from. If you compile your app on on build, and then try to use the RSLs from another one(ie. you switched machines/reinstalled the sdk/use another ide that uses a different sdk version, etc.) you will get a message when your app loads about RSL 1 loading(but it never will). So, if you reinstall the SDK, or any of the things I mentioned recompile your app with the new version. *phew*

I hope these tips are helpful to you!

Anyway, I came upon a case where I needed to know the type a variable was so I could cast it properly(and for debugging), and I found that Flex doesn’t have a function to simply return a variable’s type. There is describeType(), but this returns an XML object with all of the information about the variable — not just the type. Plus you have to import the proper class to use it. So, I threw together this function quickly that will perform the import, and return/alert the type as needed:

private function getType(value:*, alert:Boolean = false):String
{
	import flash.utils.*;
	var description:XML = describeType(value);
	if(alert)
		Alert.show(description[0].@name);
	return description[0].@name;
}

I hope someone else can find it useful.

Update: This appears to be fixed in the latest version of the plugin. I was able to enable the plugin and browse around without getting errors. But I don’t see the need for this plugin in WP installs newer than 2.6 anyway.