Microsoft refuses to comment as .NET developers fret about Windows 8

Re:Microsoft refuses to comment as .NET developers fret abou... by chrisjsmith on Friday June 03, 2011 @08:32AM (#2616064)

Same trouble here. My (work) workstation is a Dual Xeon, 12Gb RAM, SAS 15k disks (to replace the crap SSDs Dell shipped with the machines). We have (using CLOC) about 250K lines of C# (!). MVC3/NHibernate etc. Takes FOREVER to compile and run (3-4 minutes per change). Resharper is unusable. Crashes every 30 mins or so. Using SP1.

I get the same with Microsoft Connect as well. It's a disaster zone.

I hate working with the stack.

[ Parent | on HN ]

Re:Microsoft refuses to comment as .NET developers fret abou... by taway990 on Friday June 03, 2011 @11:06AM (#2616611)

>Resharper is unusable.

That has been true in most every version of VS I have used...almost like Resharper itself sucks from a software engineering point...hmmmm

>Crashes every 30 mins or so. Using SP1.

Try taking off Resharper. I hate how Visual Studio is so unguarded against poorly written components / extensions, but it is. The single biggest point of slowness / crashes I have ever seen is in third party crap, they just figure you'll blame Visual Studio so they don't care.

[ Parent | on HN ]

Re:Microsoft refuses to comment as .NET developers fret abou... by chrisjsmith on Friday June 03, 2011 @11:39AM (#2616753)

Ack I don't use R# any more TBH. Dies every 30 mins rather than ever 15 without it so it's a little better... I use the productivity power tools which is good enough.

You can probably find much ranting about R# on stackoverflow from myself.

[ Parent | on HN ]

Re:Microsoft refuses to comment as .NET developers fret abou... by jimbobimbo on Friday June 03, 2011 @10:50AM (#2616530)

I would start with removing Resharper first. While I understand why people like having it around, I've seen it degrading performance of otherwise perfectly capable setup on the same solution which flies on a similar setup without Resharper.

[ Parent | on HN ]