: [flexcoders] Flex2.0:
MXMLC compiler is a big pain during migration from 1.5 to 2.0
if you had unit tests
everything would be linked autmatically to the compiler. a good argument for
best practises no...
anyway, i suggest you check out this:
http://www.lennel.org/blog/2006/03/02/an-advantage
I am trying to migrate an application that we developed in Flex 1.5 to Flex 2.0.
These are the steps I followed:
1. Created a project in Flex 2 builder with empty content.
2. Copied MXML folders/files
3. Copied AS folders/files and Cairngorm 2 packages
4. Modified all my AS files to follow
if you had unit tests everything would be linked autmatically to the compiler. a good argument for best practises no...
anyway, i suggest you check out this:
http://www.lennel.org/blog/2006/03/02/an-advantage-of-unit-testing-with-flex2as3/
and this: someone said beta 2 is being released pretty
what i forfot to say with betya 2 being released soon, i am not certain what parts of the unit test template will break. so just keep that in mindOn 3/20/06,
Johannes Nel [EMAIL PROTECTED] wrote:
if you had unit tests everything would be linked autmatically to the compiler. a good argument for
i updated the templates to reflect beta 2 btw. will still work with beta 1 as well.On 3/20/06, Michael Schmalle
[EMAIL PROTECTED] wrote:
6. Modified Void to void for all the functions. (this is the stupidest thing in the world)
No it's not. as you can see null has always been null. Just
5 matches
Mail list logo
