It is definitely my impression that the answer to each of your questions below is -- as you expect -- no. It is possible that running a .NET app could cause the system to begin to monitor some subset of the available .NET-related Performance Counters, the data (and perhaps a trivial amount of code that won't get called) for which would continue to consume memory after the .NET apps shut down. However, I don't think you could measure the impact of that compared to -- for example -- the amount of memory used by a random unmanaged application having created a window or dialog because some part of the app was used, vs that memory not being used because you had not visited that part of the app. In other words, it would be some small number of Kbytes, virtually "noise" on our multi-megabyte machines.
At 10:44 PM 12/28/2004, Andy Smith wrote >Thanks for your replies. I guess my fundamental questions are: > >1.) Does the .NET framework have ANY effect on my computer BEFORE I start >up my first .NET application? Does it run/alter any services? Does it >change the kernel in any way? Does unmanaged code suffer at all, even >before I've run my first .NET app? > >2.) Is there any effect AFTER I shut down a .NET app (console app, not >ASP.NET)? Is there any residue, anything left running that might affect >performance of unmananged applications? > >My guess is no, because I've read that the .NET framework is "implemented >as a set of DLLs" (or something to that effect), but I don't know if >there's more going on under the covers. > >Thanks again! > >Andy J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
