Hi guys, has anyone tried to purify filesystemwatcher code? I changed the common language runtime support to clr, but when running this i got a whole bunch of errors such as :
Purify: While processing file C:\WINNT\assembly\NativeImages_v2.0.50727_32\mscor lib\9adb89fa22fd5b4ce433b5aca7fb1b07\mscorlib.ni.d ll:
Error: Read only 0 bytes, out of 0, from file C:\WINNT\assembly\NativeImages_v2.0.50727_32\mscor lib\9adb89fa22fd5b4ce433b5aca7fb1b07\mscorlib.ni.d ll.
i then set the common language runtime support to Pure MSIL Common Language Runtime Support (/clr:pure) , this got rid of the error message but i still do not get any results of memory leak issues displayed...
any help you can give would greatly be appreciated,
also i have noticed when one of the event handlers are invoked the process size gets larger.... (this is the example code on the msdn site i am running)
What do you expect Purify to do? The process size getting larger is probably not a leak, but the garbage collector at work. Did you include a real memory leak to check if Purify will find it?
i tried that already but purifier does not display any results at all, i am using visual studio 2008 btw. I am using IBM rational purifyplus. Has anyone else managed to purify the code in here:
FileSystemWatcher Class (System.IO)