Converting a project to Unicode: Part 2 ('Sorry, you're not my type.' 'Um, maybe I could change that?')

by Michael S. Kaplan, published on 2006/12/29 06:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/12/29/1377788.aspx

Previous posts in this series (including today's!):

• Part 0 (The introduction)
• Part 1 (Business before pleasure)
• Part 2 ('Sorry, you're not my type.' 'Um, maybe I could change that?)

The alternate title of this post is not something I would ever recommend using in a conversation about a relationship! 

Ok, first we'll start with the source code, you can either get it from the Platform SDK as I pointed out in Part 1, in the Samples\SysMgmt\Msi\setup.exe\ folder, or you can just download it from right here. So far nothing has happened to it -- this is our Tabula Rasa.

So now let's start dirtying it. :-)

I am going to stick it in its own folder (E:\SETUP.EXE\), navigate there from within Visual Studio 2005 Command Prompt and use either NMAKE to do a build (I have tested with the Platform SDK command prompt and others as well, the steps should work either way).

For starters, I'll make sure it can build:

Ok, good start. We probably won't be seeing success much until we are done so let's not get too used to it!

The first thing that has to happen is a search for uses of Unicode that are happening now -- obvious ones like types such as WCHAR, LPWSTR, and LPCWSTR. Clearly if there is anything that supports Unicode now we want to know where it is so that we can look at it more closely later when we decide what to do with it. Here are the results:

Find all "WCHAR", Whole word, Subfolders, Find Results 1, "All Open Documents"
E:\setup.exe\vertrust.cpp(193): WCHAR *szwSetup = 0;
E:\setup.exe\vertrust.cpp(194): WCHAR *szwPackage = 0;
E:\setup.exe\vertrust.cpp(226): szwSetup = new WCHAR[cchWide];
E:\setup.exe\vertrust.cpp(256): szwPackage = new WCHAR[cchWide];
E:\setup.exe\utils.cpp(232): WCHAR *pch = 0;
E:\setup.exe\utils.cpp(238): if ((pch = (WCHAR*)LockResource(hGlobal)) != 0)
Matching lines: 6 Matching files: 6 Total files searched: 10

Find all "LPCWSTR", Whole word, Subfolders, Find Results 1, "All Open Documents"
E:\setup.exe\vertrust.cpp(62):itvEnum IsFileTrusted(LPCWSTR lpwFile, HWND hwndParent, DWORD dwUIChoice, bool *pfIsSigned, PCCERT_CONTEXT *ppcSigner)
E:\setup.exe\setupui.h(87): HRESULT __stdcall OnProgress(ULONG ulProgress, ULONG ulProgressMax, ULONG ulStatusCode, LPCWSTR szStatusText);
E:\setup.exe\setupui.h(88): HRESULT __stdcall OnStopBinding(HRESULT, LPCWSTR ) {return S_OK;}
E:\setup.exe\setupui.cpp(372):HRESULT CDownloadBindStatusCallback::OnProgress(ULONG ulProgress, ULONG ulProgressMax, ULONG ulStatusCode, LPCWSTR /*szStatusText*/)
E:\setup.exe\setup.h(85):itvEnum IsFileTrusted(LPCWSTR szwFile, HWND hwndParent, DWORD dwUIChoice, bool *pfIsSigned, PCCERT_CONTEXT *ppcSigner);
Matching lines: 5 Matching files: 6 Total files searched: 10

Find all "LPWSTR", Whole word, Subfolders, Find Results 1, "All Open Documents"
Matching lines: 0 Matching files: 0 Total files searched: 10

Find all "MultiByteToWideChar", Whole word, Subfolders, Find Results 1, "All Open Documents"
E:\setup.exe\vertrust.cpp(225): cchWide = MultiByteToWideChar(CP_ACP, 0, szSetupExe, -1, 0, 0);
E:\setup.exe\vertrust.cpp(233): if (0 == MultiByteToWideChar(CP_ACP, 0, szSetupExe, -1, szwSetup, cchWide))
E:\setup.exe\vertrust.cpp(255): cchWide = MultiByteToWideChar(CP_ACP, 0, szPackage, -1, 0, 0);
E:\setup.exe\vertrust.cpp(263): if (0 == MultiByteToWideChar(CP_ACP, 0, szPackage, -1, szwPackage, cchWide))
Matching lines: 4 Matching files: 6 Total files searched: 10

We'll set these lists aside for later, now that we know what they are.

Now of course this sets us up to the first set of changes -- using the handy dandy Replace in Files dialog:

Note the important settings here -- all open documents, match whole words, and using the Find Next button to review followed by the Replace button if we like the change.

LPSTR -> LPTSTR (less than 25 occurrences, no surprises other than perhaps a few that are on our "review later" list)

LPCSTR -> LPCTSTR (less than 100 occurrences, no surprises)

char --> TCHAR (over 100 occurrences, no big surprises in any of them)

Well, there are actually a few issues here that I will be talking about in later posts, but we're starting with the simple approach. :-)

And of course with these changes, note that we are not doing Unicode builds yet, so that so far the build will keep working.

Some things to look forward to here that I'll be talking about in upcoming posts:

• hardcoded strings
• GetProcAddress calls
• A few specialty functions
• Some cch/cb issues
• a few non-Unicode ("A") functions being called specifically
• The MSLU/Win9x question

Believe it or not, what was done today is likely the second most widespread change we'll have to do for this project!

Wasn't that easy? :-)

Stay tuned for the next step....

This post brought to you by ഗ (U+0d17, a.k.a. MALAYALAM LETTER GA)

Mihai on 29 Dec 2006 7:07 PM:

Michael S. Kaplan on 29 Dec 2006 7:58 PM:

Michael S. Kaplan on 29 Dec 2006 11:28 PM:

Mihai on 29 Dec 2006 11:43 PM:

Michael S. Kaplan on 29 Dec 2006 11:54 PM:

referenced by

go to newer or older post, or back to index or month or day