I'm having some issues with FlashDevelop connecting to the Debugger properly, which seem to be different from the top thread, so I'm starting a new one.

I've got .NET versions 2.0, 3.0, 3.5 SP1, 4.0 and I'm running Windows XP Pro SP3.

About a month ago my debugger stopped connecting to Flash Player when I tested a program. It would put up a little progress bar and say it was trying to connect to Flash Player but it wouldn't, and it would even keep trying after I closed the flash player. I had to manually push the 'stop' button on the debugger. I went on vacation after it started so I'm only now getting around to doing something about it.

I tried to solve the problem on my own first. I figured I must have accidentally installed a non-debug version of Flash without realizing, so I reinstalled the Debug activex control. That didn't make any difference. At this time I decided to try some of my other projects to see if it was just my current one that was having troubles. I discovered that the problem was only happening with Haxe projects; AS3 projects were connecting to the debugger just fine.

I tried installing the debugger plugin for netscape to see if that would make any difference, and it did. Since I installed that, the debugger seems to connect fine, however none of my Haxe projects run. I just get flash player with a blank white background, and no errors or anything. Again, I tried AS3 projects and they work fine, debug fine, everything is normal. This is only happening with my Haxe projects.

Does anybody have some ideas for what I could try next?

Here's a link to my coding blog; it's pretty much the same thing in different words.

http://www.electricsquirrel.net/2012/08 ... -troubles/

Check in your Haxe project settings' Compiler options if Flash Debug is enabled.

Also try a FD dev build:
http://flashdevelop.org/community/viewt ... f=9&t=3529

I was able to get it working, but I'm not sure what actually fixed it. Part-way through the fixing, I realized that the project I was testing with was actually a different project with a similar name. But, after updating to the latest build it seems to be working again.