Nope, must reboot for it to take effect. My Blog[^] FFRF[^]

Hi robert, yes, i checked and it was starting perfectly.after being installed with installutil.any idea what is causing the problem.thanks in Advance. Rakesh

GetDirectories Ankit Aneja "Nothing is impossible. The word itself says - I M possible"

Hello rakesh, Plz Build solution every time whenever you want to debug it. Becoz it is possible that debugger will take old build solution & may give message that original source may change. Regards, Divyang Mithaiwala. Best of luck.

From the documentation. [lock] marks a statement block as a critical section by obtaining the mutual-exclusion lock for a given object, executing a statement, and then releasing the lock However, you do not have the guarantee that it acts like a queue, only mutual exclusion on a thread-level basis. If you have an infinite condition in your lock block, then all other threads will wait forever. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty

I know this is along time ago. But I was wondering if you would post the code that worked for you. The links pointed to in this thread don't work any more. Thanks Brent

Hi Dave, Thanks for your reply.Actually using the IShellFolder and IShellFolder2 interface was the first thing which i had tried.but i didn't have any success with them then i tried to get it through registry.Basically i want to know the sort order for a particular folder view if there is any.Hopefully by using IShellView or IShellFolder2 i can get some useful information.This is the code which i had tried. IntPtr newPidl = IntPtr.Zero ; IShellFolder ishFolder = null; IntPtr ppvOut = IntPtr.Zero; string path = @"C:\Documents and Settings\Administrator\Desktop\A"; if(Interop.SHGetDesktopFolder(ref ishFolder)==0) { // we have it: int cParsed = 0; int afItem = 0; ishFolder.ParseDisplayName( IntPtr.Zero, IntPtr.Zero, path, out cParsed, out newPidl, out afItem); IntPtr handle = IntPtr.Zero; WIN32_FIND_DATA data = new WIN32_FIND_DATA(); handle = Class2.FindFirstFile(path,out data); //here i am getting the error ishFolder.CreateViewObject(handle,ref IID_IShellFolder2,out ppvOut); ****************************************************** but i was not able to get any folder even IShellFolder interface itself from the CreateViewObject function.This is The error i got:: System.InvalidCastException: No such interface supported at TestApplication.IShellFolder.CreateViewObject(IntPtr hwndOwner, Guid& riid, IntPtr& ppvOut) How can i get IshellFolder2 or IShellView interface for any folder.what i am doing wrong here? Also thanks for the .ini link but i don't think it is going to solve my problem.Any ideas will be greatly appreciated.Thanks in Advance. Rakesh

Thanks for your reply.I know windows is case insensitive.In files case the case can be changed using MoveTo method of filesysteminfo class.it changes the case .is there any equivalent for directory may be any api or anything.thanks again. Rakesh

I'm getting confused between IconHandler and IconOverlay aren't i. Handlers let you stop the caching, overlays don't. You get exactly one overlay per object any duplications being handled by the priority flag and call ordering. In order to get a different overlay you should just be able to return a different icon or offset into the icon resource assembly and it'll work. However be aware that the shell only allows a total of 16 overlay icons so if y ou've already got the system ones and the tortoise ones present you may well run out if you use any more.

No, there isn't. What are you trying to do accomplish with this?

Without writing your monitoring code as an NTFS extension, no there is no reliable method to capture changes acrossed an entire volume. FileMon, from SysInternals, uses this technique. It requires a black belt in NTFS internals and Interop to implement though. The FileSystemWatcher relys on the NT Kernel function ReadDirectoryChangesW. This function is known to have more than a few problems, especially when monitoring remote directories. The problems just get worse, the bigger the directory tree you're monitoring. For more information, search for ReadDirectoryChangesW on MSDN. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

In C# the easiest way to accomplish this is to use a lock on an object. private static object sLock = new object(); private void Timer\_elapsed(object source, EventArgs e) { lock (sLock) { //Timer code here. } } private void FileWatcher\_event(object source, EventArgs e) { lock (sLock) { //File code here. } } any code in the lock blocks is protected from multiple threads accessing it at the same time. I do something similar with the timer that I wrote: http://www.codeproject.com/dotnet/ABTransClockArticle.asp[^] I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon

"Being modified" can't be tracked. In the case of Notepad, it opens the file, reads it, then closes it. When the file is saved, the filename is opened, written, then closed. That's it. Excel/Word is almost the same way, but they involve saving to temp files, deleting the originals, and renaming the temps file to the old filenames. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome