Is it only me, or other mobile developers experience similar incovinience, too? When I open the newsletter mail on my mobile phone, it looks bad, because it is layed out in two columns, The mobile browsers don't handle two columns very well, yet. I believe that single column layout would better serve the community of mobile developers.

No, W will not be enough: the windows that are created w/o the W are non-unicode windows (there is a special API to check the Unicodeness of a window), and they cannot accept unicode strings in menus and other places; the system standard controls, like editbox or button, do support unicode, but the top level windows and dialogs must be created differently. Cheers, Alex

Oh you don't really want to rewrite the crypto code in C# for your project. All Web security is based on standards, all the algorithms are built into .Net framework, and most importantly - the administration part of handling the certificates, public/private keys and such. This means that you can port the C code, but the result will be unmanageable: the administrators who know how to work with .Net servers, have no idea how it is done for PHP; the administrators who run PHP servers, do not know how to deal with .Net security policies. And no one knows how your solution will work when Microsoft issues the next security update. I strongly recommend to use .Net native cryptography, even if you need to learn it or use an external expert. Cheers, Alex

first, call listControl->InsertItem(&item); Your first call //Name listControl->InsertItem(i, (LPCTSTR)printableAttributes-> name->c_str()); should be converted to listControl->SetItemText(i, 0, (LPCTSTR)printableAttributes-> name->c_str()); BTW, why do you cast to LPCTSTR? If you have your Unicode setting right, it should compile cleanly without the cast; if your Unicode settings are wrong, the cast will not help at runtime. Cheers, Alex

There may be numerous advantages for Git, but it is not tuned to run on Windows. There are no VS add-ons, no shell extensions, and essentially no GUI for Git. It will be a deathly blow to any development team upgrading from Microsoft VSS. Cheers, Alex

What you should keep in mind when considering upgrade: Subversion is less tightly coupled with the Visual Studio than VSS. The MS Team System (which uses a Perforce-derived Source Control product) provides much better intergation of the development and testing cycle. In my experience, developers tend to forget some files not updated, tasks not closed, projects out of sync with the files used inside - SV cannot enforce such discipline. The Team System comes with built-in bug and change tracking capabilities, while for Subversion you must provide a separate product. It could be free, like Bugzilla, though. The big advantage of SV is that it is free; you can have the Tortoise installed on all computers, including graphical artists, technical writers, etc. The migration procedures from VSS are available, but you should remember that the underlying models are very different, therefore the whole picture of your product will look different in Subversion or in Perforce. Cheers, Alex

Only that for VS 2005 it will be msvcrt80.dll and a bunch of others. Also you need manifest files for these DLLs if you run it on Windows XP.

Hi, I just came across two bugs in the Wizard, regarding the preformatted code: - If I choose "C++", nothing is highlighted, because the formatting engine looks for "c++" and the wizard inserts "C++". - If I choose "managed C++", the case is correct, but the highlighting performs "greedy" search on double quotes (") for strings, and marks dozens of lines as string.

Small corretion, please. The problem was really in MS code for assert(). This assert() was not initialized correctly, and tried to use an unexisting stderr. Therefore, instead of displaying an assertion message, the application aborted with "Terminated in an unusual way". The problem was that the static variable initialization happened before he could use the patch suggested by Microsoft. Therefore the only way to fix it all was to find and cure the origin of assertion.