{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 女痞 的问题《How do I speed up visual studio with a large numbe》','https://www.manongdao.com/q-342911.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
This question already has an answer here:
Visual Studio 2005 is very slow with a solution with 21 projects. Any ideas how to speed it up?
相关问题
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- Visual Studio 2019 - error MSB8020: The build tool
- 'System.Threading.ThreadAbortException' in
- VS2017 RC - The following error occurred when tryi
相关文章
- How to show location of errors, references to memb
- How to track MongoDB requests from a console appli
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- Copy different file to output directory for releas
- Edit & Continue doesn't work
- “Csc.exe” exited with code -1073741819
- Visual Studio: Is there an incremental search for
I don't have VS open in front of me right now...but its roughly this...
Go to..
Tools > options > Build and release options.
Select - build startup project and dependencies only.
This will significantly speed up the process.
There are a whole bunch of suggestions in this question: Very slow compile times on Visual Studio. A combination of a few of these will definitely help to some degree
a) Buy more memory b) Break up into different solutions c) Upgrade to VS 2008 d) http://geekswithblogs.net/Ahmed_Hussein_blog/archive/2007/11/12/116791.aspx
Here's some good tips on improving VS compile speed:
ScottGu has said hard drive speed is one of the most important factors in VS performance. When we got new computers at work recently I requested that they have a second top-of-the-line hard drive. My Development folder is on my D: drive and VS loads and compiles 20+ project solutions in a matter of seconds.
Upgrading to 2008 is worth it for your situation. At my last job, we had 50 projects, and VS 2005 was dog slow. Plus it was a pain to debug (w/ multithreading). The IDE kept blowing up on us. As soon as we upgraded to VS 2008, everything went faster, the compiles went faster (partially because MS implemented a smart parallelization algorithm by the looks of it), it uses less RAM, and is far more stable.
The only regret we had with 2008 is in the C++ end of things (most of our app was VB.Net, some C#, and some C++). The new version of C++ doesn't support Windows NT which we needed to do. The workaround is a postevent that uses an old Edit Bin and sets the version for 4.0.