Yesterday, my colleague told me that he deleted some of the WEB methods in the WebService class. As a result, he found that our client program runs less nearly twenty megaby (20MB) memory space. Ah ~ How did I ignore this important factor? ! As the project progresses, our WebService has been following up, there is a considerable WebMethod that is left in the historical version, accumulated, although it is no longer used, but because we are worried that these methods will affect other modules, Therefore, I have been retained. Because the client's WebService Agent class will generate all WebMethod proxy methods, this directly leads to the volume of the client WebService agent class, and the huge WebService agent instance will take up a lot of memory. Based on this issue, we recommend that the WebService class should be planned according to system logic, do not put all the operation methods in a WebService class; create a related WebService class when using. Advocate as soon as possible, try to release it as early as possible.
"Write faster managed code: understand the overhead" http://www.microsoft.com/china/msdn/library/rchives/fastmanagedCode.asp
"Designer Getting Started" http://www.microsoft.com/china/msdn/library/EnterpriseDevelopment/softwareDev/sdaskgui08202002.mspx
