Potentially... In my opinion, for that to happen, cross platform game developers (ie, people that write for PS3, 360, Revolution, NGC, XBOX, PSP, DS and PC/Mac) - write their code in C++/C. A company that develops for just the PC is probably more likely to switch to C# than one that develops for multiple platforms. If you're interested, read more of what I have to say at my DirectX9 site. - Segment Fault

Using Win32/VC++, I want to scan the users My Pictures folder (and potentially any other user/system folder using: g_hFind= FindFirstFile( "*.jpg", &g_FindFileData); and FindNextFile(g_hFind, &g_FindFileData) ) How do I set the "working" folder so that I don't need to include the path name as part of the file path? hr = SHGetSpecialFolderLocation(0, CSIDL_COMMON_PICTURES, &pidlDocFiles); Thanks in advance, If you're interested, read more of what I have to say my DirectX9 site. - Segment Fault

Very few game developers (I can't think of ANY) use C# for programming their game engines. You will find C# used on the production, tool side of things (ie, creating level editors, particle editors, artist tools, etc). The majority of PC engine related code is written in C++/C - with pieces of it in assembly (very few nowadays -- HLSL is now showing up in a lot of new games). On the console side of things, most games are written in C++/C. STL useage is minimal (mainly in tools), template useage in general is growing.. but can lead to hiding all sorts of performance issues (or causing them). In general, stick with C++. You can use D3DX (the extensions) to get a game shell up and running in practically no time -- as well as help in loading models, textures from your favorite art packages. Hope that helps. Read more of what I have to say at http://directx9.blogspot.com/

I'd suggesting creating a typdef as follows: typedef unsigned char to BYTE; BYTE's are pretty useful in walking through raw data streams, manipulating graphics by having to twiddle the bits of various pixels, etc. Read more of what I have to say at http://directx9.blogspot.com/

I'd reiterate the earlier comment that you should BE VERY CAREFUL mixing ++i and i++. It's very easy to skip index 0 in situations where you pre-increment.. only to cause bugs that are sometimes subtle -- especially when dealing with interating through arrays of data. Read more of what I have to say at http://directx9.blogspot.com/

The most important thing to do is to always use the "sizeof" operation in any code you're referring to. Never, ever hardcode the size into your code. When reading/writing to a file - there are exceptions -- in general, avoid using "int" as a type when it comes to storage of data structures. Instead, define types such as DWORD, WORD, BYTE, etc. This will save you a lot of trouble down the road. Read more of what I have to say at http://directx9.blogspot.com/

I wonder if there is a MACRO somewhere in your code that uses 'THIS' in place of 'this'? Search for all references to 'THIS' -- what do you get? Read more of what I have to say at http://directx9.blogspot.com/