My first thought when I read mention of this was *drool*. I find I am more and more able to comfortably do basic c# for functionality – partly because of intellisense. But most of XAML to me makes sense – it feels like HTML with a kick, but I wonder what I’m missing at times?
Well, that’s when I tend to hop into Visual Studio – but why when I could have Intellisense in blend?
I say – cool! But then I kept reading.
Sounds like something that even the most adventurous designer might quail from, but just to see how far down the rabbit hole I’d have to go, I decided to read on.
Apparently this is actually a few months old – so old news. But its good to get the word out no matter how late to the catch, right?
But I have to ask myself – do I really use Intellisense for XAML?
The answer: Nope – not so much.
So why use Visual Studio for XAML?
The organization. I love the ability to “minimize” huge blocks of code. Wait – I didn’t make that emphatic enough. I LOVE the ability to minimize huge blocks of code.
So here are my thoughts: Blend is still a work in progress. Microsoft keeps adding more and more to the program, and there have been whispers about a Blend 3 being more public knowledge come Mix 09 (wish I could go…). I wonder if perhaps intellisense will be part of Blend 3 – with full compatibility?