So, as many of you Flex developers have encountered this problem in the past, it is still very frustrating when the flash player updates since it breaks my Flash Builder debug setup.
The dreaded problem when debugging a Flex application is getting an error something along the lines of:
Flash builder can’t locate debugger + NPSWF64_11_2_202_228.dll
A solution that worked for me in the past is found here:
http://www.timo-ernst.net/2010/04/chrome-flash-debugger-not-connecting-to-flexflash-builder/
This time around, when updating to Flash Player 11.2.202.228, I started seeing the same annoying message from Flash Builder.
Here’s how I solved this (on my Window 7 machine). Apparently there were two separate installations of the Flash Player (debugger) in my machine. One under C:\Windows\SysWOW64\Macromed\Flash and the other under C:\Windows\System32\Macromed\Flash. The problem was that Chrome was pointing to a different version of the player and Flash Builder to another.
Chrome version:
Flash Builder was looking at the version under C:\Windows\System32\Macromed\Flash.
All I had to do now was change the “Path” value of the Flash player under the Registry Editor and all was well after this:
Hopefully this will help some other frustrated soul out there. 🙂
FYI, this is a nifty little app that shows you which version of the Flash player you have installed as well as whether or not you have the debugger installed: http://flashplayerversion.com/