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) :)
The story is still unfinished put it that way. From: [email protected] [mailto:[email protected]] On Behalf Of Steven Nagy Sent: Sunday, March 28, 2010 8:17 PM To: ozWPF; [email protected] Subject: RE: intellisense cache in vs 2k8 Probably like most of you I tend to have Expression Blend and VS2010 open together, switching between apps to build my UI's. I only wish Blend was a little more tolerant of VS projects it doesn't know how to handle (eg database projects, WIX, etc). Sometimes it still lets me open the solution other times it totally flakes and refuses to open anything. Steven Nagy Readify | Senior Developer M: +61 404 044 513 | E: [email protected]<sip:[email protected]> | B: azure.snagy.name<http://azure.snagy.name/> From: [email protected] [mailto:[email protected]] On Behalf Of Scott Barnes Sent: Sunday, 28 March 2010 6:52 PM To: ozWPF; [email protected] Subject: RE: intellisense cache in vs 2k8 design surface = xaml view From: [email protected] [mailto:[email protected]] On Behalf Of Joseph Cooney Sent: Sunday, March 28, 2010 7:33 PM To: [email protected]; ozWPF Subject: Re: intellisense cache in vs 2k8 There's a designer????? who knew? On Sun, Mar 28, 2010 at 6:30 PM, silky <[email protected]<mailto:[email protected]>> wrote: On Sun, Mar 28, 2010 at 6:38 PM, Scott Barnes <[email protected]<mailto:[email protected]>> wrote: > I don't have R# installed and I often get crashes with VS2010 RC due to > intellisense. I'd wager that the intellisense isn't fully RC ready atm and > I'm hoping praying it fixes itself for RTM/RTW otherwise it will be a bitter > pill to swallow for VS2010. I've installed a patch for VS2010 which did > prevent some of the crashes but it hasn't removed the total pain as yet. > > As for VS2008, you're not going to get a stellar result here given the > design surface for VS2008 for XAML seems to have been jammed into place > (i.e. I used to see a lot of customer complaints about the design surface in > general with VS2008 and I'd often ask other guys in my team wtf the cider > team were working on only to get *shrugs*.. so I'm putting that down to > they're optimised more for VS2010 than fixing its current release in VS2008) I don't use the designer at all. > My 2c. -- silky http://www.programmingbranch.com/ _______________________________________________ ozwpf mailing list [email protected]<mailto:[email protected]> http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
