I don't know what you don't like about it.
It is not about disliking it. It is about the thing not working and Atmel not being honest in my view.
I don't care much about the Visual Studio features. Frankly said, if you need stuff like IntelliSense, syntax highlighting and whatnot, to not lose track of what is going in your source code for a little microcontroller, then, well, you should probably consider another job. Visual Studio is just useless ballast, cracking a nut with a sledgehammer, for lack of (that manager kid?) having a clue. If you can't think, then VS won't think for you, and thinking is the most important task when coding.
What I do care about are the basics. Like, for example, the thing installing hassle-free. Or the thing starting up fast, and then, believe it or not, the thing working. Call it as much a Beta as you like. It isn't complete, and as such doesn't deserve Beta status. And Atmel conveniently likes to forget to mention that it is a Beta in interviews and the like.
I also care about a company being honest. The
articlepress release I mentioned is not what I call honest.
Regarding
AVR Toolchain and
WinAvr, they are not the same, and it is not just a renaming.
WinAvr was indeed build by an Atmel employ, but on his own time, without support from Atmel. But Atmel didn't take
WinAvr for AVR Studio 5. Someone (that manager kid?) decided they need to do their own toolchain, and got a team within Atmel to start all over again, producing the
AVR Toolchain. A bad case of not-invented-here syndrome.
Coming back to the
I care about a company being honest thing, Atmel added some proprietary extensions to the GCC in the
AVR Toolchain. Last time I checked, people were still busy convincing Atmel that the GPL applies to them, too, and that they are required to release the source code. I don't call this Atmel behavior honest.