You don't lock the application. That isn't an effective solution, rather,
you lock the resource which you want to use. If you need to protect against
access from within your application, use a critical section. If you are
locking to protect resources which may be used outside the application, you
would need a stronger kernel level lock. Make sense?
This is a good starter article for you. The principle applies to asp.net
programming as well. watch for line wrap
http://msdn.microsoft.com/library/de...ms06112002.asp
--
Regards,
Alvin Bruney
Got tidbits? Get it here...
http://tinyurl.com/2bz4t
"Martin" <du***@somewhere.nl> wrote in message
news:3f***********************@news.euronet.nl...
Is there an ASP.NET way to temporarily claim the process in order to for
instance write to a shared file? Like Application.Lock but then not just
for the application object but truely for the application?