hi, try to following this steps. Clean your solution. Delete all files and folders from your drop site. Rebuild all. Republish. On the client side, remove all previous versions of the deployment. Then reinstall. This fixed it for my team. Find more information on this[^] link. HTH Jinal Desai - LIVE Experience is mother of sage....

Thank you for your response!! PIEBALDconsult wrote: Can those be in their own Services? Actually, yes, and they are.. I guess I should have mentioned that part :) The way I had it implemented before I made the initial post was I pretty much let it finish everything until it was able to submit the data to the other services. But Windows spazzed out because it couldn't stop the main service until it finished the preceding operations. What I ended up doing was defining like a project "state" DataTable that could be exported and imported again when the service restarts. Your suggestion was well-taken -- pretty much made the current operation finish and then updated the project state based on that. I don't know if using a DataTable is the best approach, but it seems to work much better, since it takes considerably less time to stop the service. Still open to suggestions if you or anyone can think of a better approach, though!! I guess I'm in a C# experimentation phase :)

Thank you both for your responses. The resources and general information you gave will keep me busy and are a great starting point. Thanks so much!

A better way to wait is to use the Thread.Join[^] method. That way 1. You don't need additional logic to have the main method break out of the loop when the thread(s) exit. 2. Infinite looping uses CPU cycles, whereas Join tells the OS scheduler to not schedule the current thread until the thread passed as the parameter completes. Regards Senthil [MVP - Visual C#] _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro

I believe it works on its own thread, then invokes the events to the UI thread. If your GUI is going to stay responsive, you don't have to worry about threading at all. Just create it, set the needed properties (Path, NotifyFilter, Filter), turn on EnableRaisingEvents, hook the events you want, and handle them as needed. If I remember right, this is a port from the old VBScript library, so it's intended to be as easy to use as possible. To make sure it works that way, you might want to just be sure that you're CREATING it on the UI thread. If you don't, it might invoke events to a different thread unless you set the SynchronizingObject property to a GUI control. You can also use that same property to invoke the events onto a thread of your choosing. If you want finer control, you can skip the events entirely, create it on a dedicated background thread, and loop on the WaitForChanged method, which will block until it receives a notification. Most of the time, this is overkill. There's more detail on each of those properties and methods in the MSDN help. EDIT: Sorry, missed where you said it was a console application. In that case, you probably want to go with the last method I mentioned, looping on WaitForChanged to do everything synchronously. modified on Wednesday, March 25, 2009 11:10 AM