I see we only got a Flash Player Content Debugger for 32 bit.
Any 64bit version in sight?
I know FP 11 works on 64 bit, but I found no debugger for it ::- /
I said "content debugger". There's a big difference between a player and a content debugger. The content debugger is a player + code which allows the IDE to connect to it so you can debug stuff.
Well when there is no 64bit content debugger why Flash Builder 4.5 always asks for it?
As soon as I start to debug a project using a 32bit browser on Windows 7 64bit the IDE complains about not finding a debugger version in C:\Windows\System32\Macrmed\Flash64_11_0_1.ocx
I heard that non of the tools support 64bit debugging so using Flash Player 64 bit debugger doesn't do anything. We recommend using 32 bit version.
Flash Build issue (not recognizing right FP version) is separate isuse that you can address. This is suggestion from customer support:
"From the support side, we usually first ensure that they have actually installed the debug player. This is where probably 90% of the cases get resolved. We use the TechNotes linked below for this (http://kb2.adobe.com/cps/403/kb403009.html being the main one). Customers will install the wrong version for the browser they are using, or just not complete the install at all. If they are using Chrome, we will follow the steps here (http://kb2.adobe.com/cps/839/cpsid_83950.html) and in the TechNote linked below. If all of these steps fail, we will uninstall the player completely and reinstall the debug player to ensure they didn’t have a corruption somewhere. This will usually fix 99% of the issues."
hope this info help.
That's a Flash Builder bug (being tracked by the team) - when IE 9+ is being launched in 32-bit mode, FB complains that debug player is not installed if 64-bit release player is installed.
Hitting "Yes" when asked if you want to continue will allow debugging to proceed normally.
I'm wondering if there is a way to have the debug version installed in Windows\SysWOW64 folder for IE32 and have the standard version installed in Windows\System32 for IE64. I am sure that IE32 and IE64 share the same registry entries, but there must be a workaround to achieve this. Any ideas?
It's a nuisance for everyone that uses Flash Builder (and possibly Adobe's other Flash development software) to have no Flash Player at all in IE64. I have to keep copying and pasting addresses from one address bar to the other.
I copied the files from the debugger version in the Windows\sysWOW64\Macromed\Flash\ folder, installed the standard 64bit Flash Player, then copied the debugger files back to Windows\sysWOW64\Macromed\Flash\ to overwrite the standard 32bit files (not Windows\system32\Macromed\Flash, of course). I had to rename the standard Flash11e.ocx file because file permissions would not let me overwrite it. Now I have Flash in IE64 and IE32. Flash Builder gives a warning message every time I debug, but it works:
Flash Builder cannot locate the required debugger version of Adobe Flash...
Do you want to try to debug with the current version?"
I click Yes and it debugs as usual with IE32. The warning is because Flash Builder reads the registry entry for the .ocx file required for Flash to work in IE64. I consider that less of a nuisance, but if I could turn off the warning message I would be happier. Perhaps Adobe could allow the debugger version to also install the standard Flash64_xxx.ocx without triggering the warning in Flash Builder.
The problem may be that Adobe cannot imagine usage scenarios of flash applications other than running them inside a web browser.
I am developing Flex based plugins for a native Windows (x32/x64) application. That host application is using the installed flash player .ocx control to execute downloaded Flex applications as plugins. It communicates with them via ExternalInterface calls.
So now my customer decided to not support the x32 architecture anymore and I am unable to debug plugins for the host application and many of the plugins will be unusable in future versions.
That IS a scenario without any alternative to a real 64bit content debugger. You just cannot say: use the 32bit InternetExplorer instead.
I'd recommend opening a feature request bug at bugbase.adobe.com and explaining your usage scenario to us. Once added, please let others know the bug's URL so that they can go and cast their votes.
I was wondering why I even need to debug a self install program on my computer in the first place that (since v9) has been resembling/acting more like apple/mac products than adobe. I may not be a technical wizard but my dad has been a programmer since I was a baby, I'm almost 32 (doesn't mean he really taught me that much in computers but I know how to point and click) and my dad never let an apple/mac product into our house EVER, 1. because of how they continue to fail, their product leaves the assembly line before they re-check it to make sure it's properly debugged such as what is happening now, nwo I know with the solar flares and ladi da people want to blame the weather and all sorts of current things going on in the world even online hackers for the problem but all I want to do is enjoy watching my favorite tv programs and I can't even do that.....why should I have to debug something that is your job to fix? if I fix it than pay me for fixing your mess. send me your paycheck. you keep the bills for your failure but send me your revenue. my family still doesn't like apple products to this day and we don't buy those, so please stop producing those type of products (that quality) we GREATLY appreciate it, although competition is nice, it's scarce. Thank you and we appreciate your responsibility in fixing your screw up.