Thank you very very much buddy, Yes that really helped and clarified a lot for me :-) I wish I can help u back some day. --- "Art happens when you least expect it."

Yes, useful comment. Thank you for your note. --- "Art happens when you least expect it."

No problem :) xacc.ide-0.1.0.12 released! Now even prettier than the last build :) Download and screenshots

Thank you leppie --- "Art happens when you least expect it."

Yes, that solved it, Thank you Andy very much :-) --- "Art happens when you least expect it."

Den2Fly wrote: So it seems there is no way to do it without windows services? yes? I doubt it. App end means what it says, your app is stopping. Den2Fly wrote: By the way it is not possible to create a windows service in a web application on the fly, isn't it ? Do you mean start one running, or create one ? You can control one. You could just run any old process, the point of a service is that you can control it from your app. Christian Graus - Microsoft MVP - C++

Thank you for your replies friends, While I am completely agree with your notes, I should say the concept I talked in my post was not a question about using or not using 'this' as the lock object. That was something interesting that I didn't know up to know and that is grouped locks (with a single lock object) togather that construct composite single critical sections, and creating INDEPENDENT critical sections by assigning different lock objects. I am excited about this because I didn't knew this before and non of my friends, thought so about lock usage. I posted here to see if anyone else see this interesting and usefull. --- "Art happens when you least expect it."

A very complete reply, the only thing I can add is a "Thank you" and that is all :-) --- "Art happens when you least expect it."

Hi there, This is a common issue that many people have, it's due to the authentication setting in the SQL server. Below is a clear explanation from a Microsoft online supporter: http://www.sql-server.org/Unauthorized_user_in_ASP_-4790415-3732-a.html[^]

You r right, when I clicked on the link it brought me MSDN index!, Now I got what u mean, I'll try it thanks. --- "Art happens when you least expect it."

I had one of these. Try to set the CLR exception to break into the debugger. In the Visual Studio .NET when a solution is open open the Debug menu and choose Exceptions. In the dialog choose the 'Common Language Runtime Exceptions'. Then change the radio button below of the 'When the exception is thrown:' to 'Break into the debugger'. This way as soon as the exception is thrown you break into the debugger and not in the place it is caught. P.S. You can restore the exceptions to their default setting by pressing the 'Clear All' button. Good luck, Ami

You are right. Thank you. --- "Art happens when you least expect it."

You can use joins to delete as well. You can also use them to update. Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer

All I can do to appreciate now is to say thanks :-) --- "Art happens when you least expect it."

Thank you, Thank you, Thank you and once more, Thank you ;-) --- "Art happens when you least expect it."

It greatly depends on what the stream is. More information would be helpful. The snippet below - depending on whether or not the stream supports seeking - would work for many cases (but certainly not all, like with a NetworkStream - but not limited to it): if (stream.CanSeek<) { stream.Seek(0, SeekOrigin.Begin); using (FileStream file = new FileStream("file.dat", FileMode.Create, FileAccess.Write, FileShare.Read)) { int read = 0; byte[] buffer = new byte[4096]; while ((read = stream.Read(buffer, 0, 4096)) > 0) { file.Write(buffer, 0, read); } file.Flush(); } } This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Sustained Engineering Microsoft [My Articles]

Yes it is solved Thank you ;-) --- "Art happens when you least expect it."