Tuesday, November 25, 2008

A practical solution to Slow VS.NET 2008 IDE

At my work, we recently migrated our codebase to ASP.NET 3.5, using VS.NET 2008 as our IDE. Needless to say, all developers were (and tosome extent are) excited. Days passed by and our hopes started diminishing. Reason? The IDE being DEAD SLOW! Our Web Project is humungous and a Ctrl-S on a file would compel us to take a break!! Believe it or not, it is that bad!

I started researching. Googling, that is :-)

And to my surprise, we were not alone in the planet. There were lot of developers going through the same pain we were having. Needless to say, it was some solace, but none of the forums, on which the complaints were pouring in, had any solid soultion. And that frustrated me!

After talking to other projects in the firm, we decided to split the web project into chunks. And this article by Scott Gu gave us courage.

We did some POCs and we think we are in the right direction.

UPDATE

The PoCs that we did have given us more courage and are comfortable in breaking our humungous solution to sub-solutions. We would have lot of happy developers... and happy developers make wonderful products!! :)

Cookies, anyone?

  Our application started having integration issues early March this year. Did I say that was intermittent? To add to our confusion, we coul...