Comments on: Tired Of Working With Big Visual Studio Solutions? http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/?utm_source=rss&utm_medium=rss&utm_campaign=tired-of-working-with-big-visual-studio-solutions Sun, 12 Feb 2012 18:54:00 +0000 hourly 1 http://wordpress.org/?v=3.0.5 By: Merill http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/comment-page-1/#comment-41601 Merill Tue, 30 Dec 2008 09:39:47 +0000 http://elegantcode.com/?p=1733#comment-41601 Having the solution on a different hard disk will solve your problem. See ScottGu's post on it here. http://weblogs.asp.net/scottgu/archive/2007/11/01/tip-trick-hard-drive-speed-and-visual-studio-performance.aspx Having the solution on a different hard disk will solve your problem. See ScottGu’s post on it here.

http://weblogs.asp.net/scottgu/archive/2007/11/01/tip-trick-hard-drive-speed-and-visual-studio-performance.aspx

]]> By: Davy Brion http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/comment-page-1/#comment-41562 Davy Brion Mon, 29 Dec 2008 19:03:22 +0000 http://elegantcode.com/?p=1733#comment-41562 @Willie you can, but it's not very practical if one of the referenced dll's is updated pretty much every hour or when you need to make changes in multiple assemblies to implement a new feature @Friend Resharper and Visual SVN definitely introduce some extra slowness, but Visual Studio itself is the main culprit... for large solutions, Visual Studio is unbearably slow regardless of whether you have resharper/visual svn installed or not @Willie

you can, but it’s not very practical if one of the referenced dll’s is updated pretty much every hour or when you need to make changes in multiple assemblies to implement a new feature

@Friend

Resharper and Visual SVN definitely introduce some extra slowness, but Visual Studio itself is the main culprit… for large solutions, Visual Studio is unbearably slow regardless of whether you have resharper/visual svn installed or not

]]> By: Friend http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/comment-page-1/#comment-41561 Friend Mon, 29 Dec 2008 18:58:21 +0000 http://elegantcode.com/?p=1733#comment-41561 most of the times, vs.net add-on's are the main problem, not the ide itself. you are using resharper, your are using visual svn (based on the above images). these add-on's monitor your codes and activities, so they will have the main impact. most of the times, vs.net add-on’s are the main problem, not the ide itself.
you are using resharper, your are using visual svn (based on the above images). these add-on’s monitor your codes and activities, so they will have the main impact.

]]> By: Willie Tilton http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/comment-page-1/#comment-41558 Willie Tilton Mon, 29 Dec 2008 18:39:15 +0000 http://elegantcode.com/?p=1733#comment-41558 Couldn't you have two totally seperate solutions, and then just reference in the dlls from the other solution? This way you could have a lib or dependencies folder, which when you build from the first solution would copy the dlls into the folder, and then when you update your code the latest dlls would be included automatically. That way you wouldn't have everyone on the team needing a rebuild and you'd still accomplish the same thing. Couldn’t you have two totally seperate solutions, and then just reference in the dlls from the other solution? This way you could have a lib or dependencies folder, which when you build from the first solution would copy the dlls into the folder, and then when you update your code the latest dlls would be included automatically. That way you wouldn’t have everyone on the team needing a rebuild and you’d still accomplish the same thing.

]]> By: Jamie Penney http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/comment-page-1/#comment-41507 Jamie Penney Mon, 29 Dec 2008 09:20:17 +0000 http://elegantcode.com/?p=1733#comment-41507 Another problem I can see with this is if you are doing any refactoring, Resharper won't pick up the references in the larger project. A good idea for a stable codebase however. Another problem I can see with this is if you are doing any refactoring, Resharper won’t pick up the references in the larger project. A good idea for a stable codebase however.

]]> By: Davy Brion http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/comment-page-1/#comment-41486 Davy Brion Mon, 29 Dec 2008 01:31:47 +0000 http://elegantcode.com/?p=1733#comment-41486 yea Resharper doesn't recognize the stuff you use from projects that you didn't include in your solution. In our case it's usually not a problem since that only happens on pages that only use the old stuff.... we don't have pages that mix the new and the old stuff. yea Resharper doesn’t recognize the stuff you use from projects that you didn’t include in your solution. In our case it’s usually not a problem since that only happens on pages that only use the old stuff…. we don’t have pages that mix the new and the old stuff.

]]> By: Sergio Pereira http://elegantcode.com/2008/12/28/tired-of-working-with-big-visual-studio-solutions/comment-page-1/#comment-41483 Sergio Pereira Mon, 29 Dec 2008 01:24:32 +0000 http://elegantcode.com/?p=1733#comment-41483 For a moment I believed this would be very helpful for me... Until I tried and Resharper went berserk on the missing references, even though VS compiles the small solution just fine. Apparently I'm destined to eternal frustration with this large solution I have to work with. For a moment I believed this would be very helpful for me… Until I tried and Resharper went berserk on the missing references, even though VS compiles the small solution just fine. Apparently I’m destined to eternal frustration with this large solution I have to work with.

]]>