I've experienced the same issues in VS2008 SP1. As a result I primarily use the xaml editor in Blend.
It's very annoying. Julian From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Monday, 15 February 2010 2:21 PM To: 'ozSilverlight' Subject: RE: XAML Intellisense lost I have found that the problem of the missing intellisense is intermittent. It will occasionally start working again, but not very often, and I can't find any pattern yet behind what's going on. Surely I'm not alone in having a Silverlight/WPF designer in Visual Studio 2008 what is broken to hell and back. Besides the mostly broken intellisense, opening XAML in the designer causes Visual Studio 2008 to randomly and frequently crash completely with the "Send or Close" dialog. It will not response to the Close button and I have to kill the devenv.exe task. If VS2008 restarts and the XAML file was the last one open, it will attempt to reopen it and crash immediately. I have to manually delete the *.suo files and restart Visual Studio. Ignoring the fact that the designer doesn't actually design anything at all -- it's just a XAML editor -- the highly unstable experience makes developing Silverlight in Visual Studio a living hell and nearly doubles my development time. At Code Camps and evening SIG meetings I never hear anyone complain about these sorts of issues. I was wondering if the experience was better in Visual Studio 2010 RC, but when I created a new Silverlight project it crashed immediately before even loading the solution. Greg
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
