Hi there, Can anyone explain why the assembly qualified names seen in the ".resx" file for each form in an application aren't kept up-to-date by Visual Studio. For instance, if a dialog uses a user control from some other library in the same solution, the user control's assembly qualified name will appear in the dialog's ".resx" file. Each time the control's library is compiled however, the library's version is incremented but the ".resx" file continues to show the original version number. How then does Visual Studio load it when the dialog is displayed in the Visual Studio designer? If all projects are signed then the control's library identity won't match what's in the '.resx" file but Visual Studio seems to ignore this. Can anyone shed any light on the situation? Thanks in advance.
GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist? When all my processign is done i set everything to null and then: GC.Collect(); and then GC.WaitForPendingFinalizers(); but it still shows that my process takes 400 MB of memory. Is there any easy way to see what references that I forgot to set to null so that the memory cleas up on GC.Collect() ?
STOP MULTI-POSTING NOW! ppl told you already... "DR" wrote in message news:enoiwF0nIHA.2292@TK2MSFTNGP03.phx.gbl... > GC.Collect() not cleaning memory, how to find out what references to lots > of memory still exist? > > When all my processign is done i set everything to null and then: > GC.Collect(); > and then > GC.WaitForPendingFinalizers(); > but it still shows that my process takes 400 MB of memory. Is there any > easy way to see what references that I forgot to set to null so that the > memory cleas up on GC.Collect() ? >
