I was always under the impression that when developing in ASP.Net you don't need to worry about releasing memory i.e. in your pages/functions/subs you can create as many variables/objects as you want, use them and then 'walk away' and let asp clear up the mess - but after doing some browsing on the web there are a number of people who do not this this is the case. Can anyone give me a definative answer on this.
i.e. if i have something like this at the top of my proc :
dim mObj as new MyClass
do i have to put mObj = nothing at the end.
What about things like collections - does the same apply ?
Finally are thare any specific things to look at / avoid to ensure that your asp.net app does not contain any memory leaks.
many thanks in advance
...
Go to the complete details ...