Even without trying 2.0 final yet, I would strongly urge you not to upgrade your main flex beta environment.  Install it on a separate computer, spend about and hour or two on just seeing what has changed.  If it takes longer, you're probably best off not doing it.

I think that's the best advice anyone here could give you.  There's no way for people to tell just what minor quirk that they don't know about will really come into play in your app.

On 6/28/06, Sonja Duijvesteijn <[EMAIL PROTECTED]> wrote:

Hi all,

I've been working on a fairly large application for the last months. This project is the final thing i need to do before graduation, so it's very important everything works. The deadline is next week tuesday (6 days away) and I would love to hand in a version that is final, in stead one working from the beta. But, as always with projects I have quite a list of last minute fixes that need to be done and I have no idea how much time it will take switching from beta 3 to the real deal.

So the question is, how much time does it take to switch over? Are there parts of code that changed drastically, are there any area's I could expect problems?

If things don't work next week it means I'll fail, won't graduate and have to do my internship all over, costing 5 months. So, I'm hesitant to jump on the boat. But man, flex 2 is tempting!

Kind regards,
Sonja Duijvesteijn




--
Jason __._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to