Using Visual Studio 2010 memory when publishing a website

I have an Asp.Net website project that is increasingly causing memory problems during publishing. Visual Studio works quite well during normal operation, and even the build phase is pretty fast (especially after following some of the recommendations in the messages listed below). However, the publishing phase is slow, and to a greater extent this is due to the fact that Visual Studio consumes from 400 to 500% of its memory on a regular basis (from 500 MB to 2.25 GB in the task manager). In addition, increased memory consumption continues for several minutes (5 or 10, in some cases) after the “Post Successful” message appears in Visual Studio. Actually, this is really a problem - I do not mind that I do not do much at the time of publication, but as soon as this is over, I want to return to work, but memory overload means that my whole system is not responsible for what looks like looong time after VS seems to do its job.

The structure of the solution is as follows:

Solution | -Web Site Project | - Data Access Layer Project | - Data Access Layer Tests 

Both DAL and some of the underlying code rely on an external library to access the ERP system, but I'm pretty careful to keep them both in the same version (in fact, I should be - some pages on the site if versions do not match). I have some more small helper libraries in which I am also very careful - in both projects they are all referenced from a shared folder. I don’t think I’m suffering from the “ Duel Build Links ”

The website is configured with the "Allow this precompiled site to be updated" checkbox enabled and the "Use fixed names and individual sites" flag enabled.

As part of this solution, the entire solution has now been launched as the VS 2005 / Asp.Net 2.0 server. We missed the year 2008 and now we are launching it under VS 2010 / Asp.Net 3.5. The problems that I see were more or less under VS2005, and definitely followed me from my old machine (which was somewhat inadequate) to this seemingly rather modern one.

The machine I'm building with is a 64-bit Win7 machine with 8 GB of memory. I am running several AddIns / Extensions in VS (specifically Telerik JustMock and DevExpress CodeRush / RefactorPro).

I looked at several other common memory / performance related threads on SO (including this and this ) and followed up on recommendations that I thought were relevant.

Has anyone else seen this or had any indications of what I could do to make it easier?

EDIT

FWIW, I publish this in a folder on my local machine, so I don’t think the problem has anything to do with network latency ...

+4
source share
1 answer

Now back to that. I moved from this position and do not experience the same problem in my new position, but the development of the “Building solution takes forEVAR” in my new position showed me to make sure that my control points were kept at a reasonable level - I had a very a lot of time for assembly, but after removing all the control points (most of which were not used), the assembly time improved ten times.

It is very possible that I was suffering from the same problem in the project mentioned in this question, so maybe this will help someone who has this problem.

+1
source

All Articles