The complaint about vector usually comes when multiple projects are targetting different SDKs. Make sure you are either building against 4 or 3.x and not a mix.
Second, if you are building against 3.x but want to target flash player 10, make sure flash builder has linked in a playerglobal.swc that is for 10 and not 9. I do compile this in both 3.x and 4.0 in Flash builder on my machine for both 9 and 10 though so it does work if everything is in sync. Sometimes you just have to fight builder.
The project is set to compile to Flash 10. At work today I will try to create a very small test project that exhibits this behaviour and then post it
If I create a very very simple Flex Project using 3.3 and flash player 10, add a class that has a Vector member in it, create a new test case class that includes that class. When running tests I DO NOT get the problem.
However If I create a very very simple Flex LIBRARY Project using 3.3 and flash player 10, add a class that has a Vector member in it, create a new test case class that includes that class. When running tests I DO get the problem.
I have attached both these projects for your perusal - exported from 262635 on an XP machine.
Let me know if I should turn tyhis into a valid bug :-)
I have exactly the same issue.
Is there a workaround ? It's rather annoying.
( Note: A possible workaround is to link all the libraries you're interested in to a dummy project and launch the tests from it )
Just got the same problem and, after reading this http://opensource.adobe.com/wiki/display/flexsdk/Targeting+Flash+Player+10 I solved it by changing target player in flex-config.xml (found in your_sdk/frameworks) to 10.0.0:
I suggest duplicating your existing SDK (presumably 3.5) to 3.5_10 and changing the flex-config.xml. That is if you have multiple projects in your workspace and you expect some of them to compile with fp 9.
Let me know if it worked out.