It does when you're job is to entice the design audience whom aren't typically Microsoft based to adopt your technology. Asking a design minded audience to take a leap of faith on a tool like Visual Studio isn't likely to yield a positive outcome. That and at the time of development, writing the necessary requirements for Blend and attempting to do the same inside VS would of slowed the evolution of WPF/Silverlight down quite dramatically as VS code base is a 10,000 lbs gorilla where as Blend is quite nimble and agile enough to cope with change.
VS2010 though should start bringing balance back to the force and both tools are likely to keep a fairly healthy amount of parity with one another when it comes to role specifics. In actuality it's really the dev audience that are struggling with which pill to swallow, the design minded audience simply appear to be aok with the initial SKU's (Blend adoption lifecycle aside). Scott. -----Original Message----- From: silky [mailto:[email protected]] Sent: Sunday, March 28, 2010 9:28 PM To: Scott Barnes Cc: ozWPF Subject: Re: intellisense cache in vs 2k8 On Sun, Mar 28, 2010 at 9:04 PM, Scott Barnes <[email protected]> wrote: > I remember this being a fairly common ask from the dev fence line. "Why > can't I do all the stuff i need to do in VS instead of blend" or "Why Can't > i do all the stuff I need in Blend instead of VS"... I used to put it down > to the "Goldilocks and 3 bears" analogy as it was and still probably a case > of chasing the right temp porridge (not too VS. and not too Blend, but just > right) J It's what happens when you make a decision to split functionality. It doesn't make a great deal of sense to go with an entirely new app, when VS already supports the model of different "roles". You can understand the general decision making process, and it's easy to say another way is better, but I think it's due to that decision anyway. So you just live with it. Not everyone can make perfect decisions :P > The story is still unfinished put it that way. -- silky http://www.programmingbranch.com/ _______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
