With VCL.NET the migration of Delphi Win32 applications to .NET will be much-much easier than before. I find that a sufficient reason for VCL.NET to exist.

InOut.NET wrote: I decided to ditch AnsiString* and go for a struct* with a few AnsiSting in it. Probably the struct * will give you the same sort of problem the AnsiString * gave (I hope the countrary, of course). :) If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.

Stephen Hewitt wrote: 3. Using abstract base classes as interfaces to avoid having to include class definitions. Yeah this is what i want to hear. I was never sure. Currently my design lacks abstraction. But now - implementing and converting candidate classes will mean a huge design change. Thanks!

InOut.NET wrote: I program in Borland using VCL :omg: I missed that :) We were referring to Windows APIs, so yes, low level. Cheers! Mark Mark Salsbery Microsoft MVP - Visual C++ This episode brought to you by the letter Z

genius, Thanks.

leppie wrote: Source control ...and Baileys! Guess what I'm doing tonight? :-> Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.

A correction to my previous statement: The lock statement doesn't lock the object per se, it only prevents the code in the lock statement (or any other lock statement using the same object) to be entered by another thread. The object is only used as an identifier, so it doesn't matter what object you use if you only have one lock statement. The lock statement calls System.Threading.Enter, which uses the Monitor class. A lock statement is the convenient form of: try { System.Threading.Ender(theObject); ... lotsa code } finally { System.Threading.Exit(theObject); } --- b { font-weight: normal; }