It also depends on how big the project is. I work for a medium sized (1400+ people) company; but the contracts I've worked on have been have been fairly small and jack of all trades are cheaper because of the amount of time that would be spent spinning up more specialists on the required domain knowledge. Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall

Absolutely. One must choose the solution that fits best, that is why testing more than one way to achieve this is the best way to find out.

Well, the below code will answer it class Program { static ReaderWriterLockSlim rwSlim = new ReaderWriterLockSlim(LockRecursionPolicy.SupportsRecursion); static void Main(string[] args) { // entering upgradable read lock rwSlim.EnterUpgradeableReadLock(); Console.WriteLine(rwSlim.IsUpgradeableReadLockHeld); // downgrading to readlock. Now you are in read lock rwSlim.EnterReadLock(); Console.WriteLine(rwSlim.IsReadLockHeld); // exiting from upgradable lock rwSlim.ExitUpgradeableReadLock(); Console.WriteLine(rwSlim.IsUpgradeableReadLockHeld); // exiting read lock rwSlim.ExitReadLock(); Console.WriteLine(rwSlim.IsReadLockHeld); } } You need to supply LockRecursionPolicy.SupportsRecursion to indicate that you need recursive locks. Navaneeth How to use google | Ask smart questions

MagicISO, I don't know if it is free or if the trial version will allow it. Why can't you mount to a virtual drive?

Cool. At least you figured it out. Simon

Yes, I edited the post and checked the return value, probably at the same time you were writing. :) Thanks. My LinkedIn Profile

Thanks a lot! My LinkedIn Profile

HosamAly wrote: have I been offensive to anyone? I don't think so. It is not like you get loads of 1-votes in your posts. HosamAly wrote: I don't get much response to my questions Well, folks answer questions when they can and if they can. "The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham

Your only chance is to use the Dispose pattern and propagate it down your object graph(s), and additionally use try/catch logic in the appropriate places. Finalizers for sure will lead you nowhere since - as stated above - they are indeterministic in order. The logic may become complicated depending on what you are doing - but there has to be one. HosamAly wrote: Another issue is when the application is rudely unloaded; If that means 'crash' or 'cancelling the app via task manager' there's exactly nothing you can do. (Anyway, this is exceptional and not part of a programs normal behaviour, so you're not really to blame for things that happen in this case.) Regards Thomas www.thomas-weller.de Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Programmer - an organism that turns coffee into software.

Thanks a lot! I'll try to check with MSDN. Meanwhile, I made this workaround, tried stopping it from within the debugger (to simulate AppDomainUnload), and it worked OK. I'm not sure how safe it is, but it seems to be working fine. class MyApp { private static SafeHandle handle = new MyAppSafeHandle(); public static KeepAlive() { GC.KeepAlive(handle); } } class MyLibSafeHandle : SafeHandle { public MyLibSafeHandle() : base(IntPtr.Zero, true) { MyApp.KeepAlive(); } protected override ReleaseHandle() { externRelease(handle); MyApp.KeepAlive(); } } My LinkedIn Profile

AFAIK, Windows Sockets will let you set it to a max size of 1MB. The receive buffer isn't meant to be a data store. For best TCP/IP performance, your user-mode code should remove ("receive") data from the socket ASAP. i.e. Send buffer should be full, receive buffer should be empty. Mark Salsbery Microsoft MVP - Visual C++ :java:

So sad :( Thanks anyway I would be grateful if you could link me to a checklist of some sort... Thanks again My LinkedIn Profile

Sorry, I noticed that this would result in a memory leak for the SafeHandle itself.

Then use conditional compilation.

If you really need to optimise the code so much that you need the methods to be inlined, you are way beyond maintainable code. If you are still thinking of maintainable code, you should not bother with the tiny performance difference that inlining methods means. Despite everything, the person most likely to be fooling you next is yourself.

You dont have problem with existing languages like c++.net or vb.net. But someone may develop a language that uses .net components, without support for unsigned integers. For such senarios stands the CLS.

Thanks

Here you are: Migrating 32-bit Managed Code to 64-bit[^] Giorgi Dalakishvili #region signature my articles My blog[^] #endregion