Are there specific APIs that you are using which have been deprecated in .NET 2.0?
We went through a similar problem at work some years ago, and they net result was that we ported to .NET 2.0 - it was a much smaller job than the continual maintenance of the old code, and given than mainstream support for .NET 1.1 ended 2 years ago, it seemed like the right thing to do. Maybe not an option for you for some other reason, but the move isn't always as difficult as you'd imagine. Our process was essentially rebuilding and redeploying everything onto our DR servers and running side by side for some time until we were sure everything was in order. On Fri, Mar 12, 2010 at 8:47 PM, mredmond <[email protected]> wrote: > Hi Folks, > > We've got a number of .NET 1.1 applications that are having horrible > memory leakage issues. Similar applications running under 2.0 do not > have nearly as many problems. On the servers having the issues, > Perfmon shows the Gen02 GC heap slowly ratcheting up until the > application fails. > > We are in the process of band-aiding the problems using app pools and > auto-restarts of the app pools when memory thresholds are reached. > This isn't a long-term solution but we're hopeful it will get the job > done for the time being. In the short-term, fixing or rewriting the > apps isn't an option, nor is porting to 2.0. > > My primary concern right now is to identify why this issue is > happening and what coding practices might prevent it in the future. > > Can anyone explain to me the differences between garbage collection in > framework versions 1.1 and 2.0? > > Is is possible that the GC in version 1.1 doesn't do a good job of > cleaning up unmanaged resources? One thing I've noticed is that our > developers *never* call the Dispose() method on objects. > > Thanks! > > >
