Alebas wrote: I mean that C++ guys helped me to find a solution of a problem, but they did not of course just re-write some piece of program using C++ to make the program working faster. I did not think that is what happened, sorry if I implied that.    I think that an understanding of the Win32 API as it relates to the functionality that is presented to you through the framework would be good to learn.  If things like Mono ever become (more?) mainstream, it would also help explain why one feature works differently faster/slower/side-effects on architecture/OS than another.  I believe that learning something a bit lower level like C/C++ would help in those areas, as well as an understanding of data structures (linked lists, hash tables, etc.) and algorithms and how they work are are implemented.    As far as assembly, I have never written any significant amount of assembly code myself.  I have replaced a memcpy(...) here and there, but nothing serious.  I think that an understanding of machine structures/architecture (how a CPU works, particularly ones you are using) and how your OS manages memory is more important, so that you begin to understand things like spatial and temporal locality when dealing with multiple items or sets of data and how they can affect performance.    Peace! -=- James If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong! Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road! DeleteFXPFiles & CheckFavorites (Please rate this post!)

It should be a fairly easy transition. It's more learning the environment and namespaces than learning a new language (except for pointers).