Comments on: .Net 3.5 Disaster & Pixel shaders! http://rob.runtothehills.org/archives/167 Talk is cheap. Show me the code. Tue, 24 Aug 2010 09:16:14 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: rob http://rob.runtothehills.org/archives/167/comment-page-1#comment-1327 rob Mon, 14 Jul 2008 16:18:33 +0000 http://runtothehills.org/rob/archives/167#comment-1327 Hi Matt, No, I didn't have that add-in installed. I notice that there were comments about having resharper though,but in the end that wasnt my problem either. Seemed that good old windows update solved my problems anyway. Cheers Rob Hi Matt,
No, I didn’t have that add-in installed. I notice that there were comments about having resharper though,but in the end that wasnt my problem either. Seemed that good old windows update solved my problems anyway.

Cheers
Rob

]]> By: Matt Valerio http://rob.runtothehills.org/archives/167/comment-page-1#comment-1326 Matt Valerio Mon, 14 Jul 2008 06:38:34 +0000 http://runtothehills.org/rob/archives/167#comment-1326 Hey Rob, I just ran into exactly the same problem as you did. I poked around (and found the same comments on ScottGu's blog) but nothing I tried helped. I detailed my experience here: <a href="http://thevalerios.net/matt/2008/07/net-35-sp1-beta-woes/" rel="nofollow">http://thevalerios.net/matt/2008/07/net-35-sp1-beta-woes/</a> In the end, it turned out that a bad addin, StudioTools, was the culprit. Out of curiosity, did you have that addin installed? Hey Rob,

I just ran into exactly the same problem as you did. I poked around (and found the same comments on ScottGu’s blog) but nothing I tried helped. I detailed my experience here:

http://thevalerios.net/matt/2008/07/net-35-sp1-beta-woes/

In the end, it turned out that a bad addin, StudioTools, was the culprit. Out of curiosity, did you have that addin installed?

]]> By: rob http://rob.runtothehills.org/archives/167/comment-page-1#comment-1323 rob Mon, 30 Jun 2008 19:01:02 +0000 http://runtothehills.org/rob/archives/167#comment-1323 Hi Chris, Yes I did managed to fix devstudio, (the next post on my blog detailed this) http://runtothehills.org/rob/archives/170 you didn't read far enough ;) Basically there are 2 updates that are available via windows update that aren't installed by default (see post), but installing those fixed the issue for me! Thanks for reading! Hi Chris,
Yes I did managed to fix devstudio, (the next post on my blog detailed this)
http://runtothehills.org/rob/archives/170
you didn’t read far enough ;)
Basically there are 2 updates that are available via windows update that aren’t installed by default (see post), but installing those fixed the issue for me!
Thanks for reading!

]]> By: Chris Madrid http://rob.runtothehills.org/archives/167/comment-page-1#comment-1322 Chris Madrid Mon, 30 Jun 2008 01:38:07 +0000 http://runtothehills.org/rob/archives/167#comment-1322 Did you find a solution? Looks like I'm in the same situation. Did you find a solution? Looks like I’m in the same situation.

]]> By: WPF/Silverlight/XAML Web News - 2008/05/23 - Rob Relyea - Xamlified http://rob.runtothehills.org/archives/167/comment-page-1#comment-1303 WPF/Silverlight/XAML Web News - 2008/05/23 - Rob Relyea - Xamlified Fri, 23 May 2008 20:27:51 +0000 http://runtothehills.org/rob/archives/167#comment-1303 [...] First .Net 3.5 Disaster & Pixel shaders! then .Net3.5 SP1 problem [...] [...] First .Net 3.5 Disaster & Pixel shaders! then .Net3.5 SP1 problem [...]

]]>