This - http://msdn2.microsoft.com/en-us/vstudio/bb510103.aspx
might change things a bit. It's basically MS's answer to eclipse, as I see it. If Adobe were to build an Flex Builder on this instead, you could probably get a lot of your wishlist. --- In [email protected], Paul deCoursey <[EMAIL PROTECTED]> wrote: > > Troy Gilbert wrote: > > > > I largely prefer many of Visual Studio's (particularly 2005) features > > to FlexBuilder, though do like some of FlexBuilder/ Eclipse's features > > as well. > > > > Of course, the features I like most about Visual Studio don't seem to > > be intrinsic to the way it does things, more just that they don't > > exist in Flex Builder. For example, Visual Studio does some incredible > > Intellisense for C#... it basically suggests appropriate text > > (keywords, variable names, types, functions, etc.) with every > > keystroke. For folks with a lame memory like myself, it's great... > > it's also very conducive to using long, descriptive names for things > > since you don't end up having to type it all out constantly. > > > > I totally agree with that one... FB/Eclipse really falls short in that > regard. > > > > > > It's also *very* smart about automatic formating of the code, and you > > can define all the rules that it applies as you type. > > > > In addition, there are some tools built into VS that need to be added > > to Flex (and sound like they may be to a degree with the data wizards > > in Flex 3), stuff like automatically generating classes from XML > > schemas, providing visual designers for schemas, etc. > > > I'm working on a Class generator from XML Schemas right now. I have a > fairly good start, still working out some bugs. I expect to have a beta > release available in the next few weeks. It's built right now as an ANT > task. > > Paul >
