| Groups | Blog | Home |
visual c : convert char * (argv[]) to wstring and to LPCWSTR
I have been looking all over the place for a method to take command line
arguments and convert them to a string or wstring so i can process the data and then covert the resulting strings to LPCWSTRs. I have tryed several methods and none work. They include: the convert utilities A2W but that does not compile because of unknow variables declared in the convert header file. MultiByteToWideChar which seems to work once but not the second time i go to use it. The problem with all the task scheduler examples is they only show how to work with literal (hardcoded) values for CPCWSTRs. and i can not find any examples of how to just convert command line arguments to LPCWSTRs. Thanks in advance, Fred
one additional requirement is that what ever i do works in the non-.NET
environment, meaning the old NT environment. [quoted text, click to view] "ka1cqd" wrote:
> I have been looking all over the place for a method to take command line > arguments and convert them to a string or wstring so i can process the data > and then covert the resulting strings to LPCWSTRs. I have tryed several > methods and none work. They include: > the convert utilities A2W but that does not compile because of unknow > variables declared in the convert header file. > MultiByteToWideChar which seems to work once but not the second time i go to > use it. > The problem with all the task scheduler examples is they only show how to > work with literal (hardcoded) values for CPCWSTRs. and i can not find any > examples of how to just convert command line arguments to LPCWSTRs. > > Thanks in advance, > Fred
I have read all the info about both methods that i could find on MSDN and
used the code examples for there and could not get them to work. I have since found, mbstowcs() which appears to work. also it appears to backward compatible. Where do i find the doucmentation on how to use the MFC/ATL?? How do you tell what version of the complier is being used? When i start it, it just says visual studio .net and if i look at the versions under help about i see a number 69586-335-0000007-18820. [quoted text, click to view] "David Wilkinson" wrote:
> ka1cqd wrote: > > > I have been looking all over the place for a method to take command line > > arguments and convert them to a string or wstring so i can process the data > > and then covert the resulting strings to LPCWSTRs. I have tryed several > > methods and none work. They include: > > the convert utilities A2W but that does not compile because of unknow > > variables declared in the convert header file. > > MultiByteToWideChar which seems to work once but not the second time i go to > > use it. > > The problem with all the task scheduler examples is they only show how to > > work with literal (hardcoded) values for CPCWSTRs. and i can not find any > > examples of how to just convert command line arguments to LPCWSTRs. > > > > Thanks in advance, > > Fred > > > > Fred: > > A2W is part of MFC/ATL so if it does not work it is because you are not > using it correctly. Did you read the documentation? > > Likewise for MultiByteToWideChar(). > > Which version of VC++ are you using? > > David Wilkinson
Hi Jochen,
if i follow what you suggested, i need to #define _UNICODE and then everything is in the wide format and i don't have to deal with the conversion? Is this correct? Thank you, Fred [quoted text, click to view] "Jochen Kalmbach [MVP]" wrote:
> Hi ka1cqd! > > I have been looking all over the place for a method to take command line > > arguments and convert them to a string or wstring so i can process the data > > and then covert the resulting strings to LPCWSTRs. I have tryed several > > methods and none work. > > Why not create a unicode-app? > And define the following entry: > > int _tmain(int argc, _TCHAR* argv[]) > > > > They include: > > the convert utilities A2W but that does not compile because of unknow > > variables declared in the convert header file. > > You shouldn´t use A2W, instead use the new ATL7 macros: > Cx like CA2CW > > -- > Greetings > Jochen > > My blog about Win32 and .NET > http://blog.kalmbachnet.de/
[quoted text, click to view]
ka1cqd wrote: > I have been looking all over the place for a method to take command line > arguments and convert them to a string or wstring so i can process the data > and then covert the resulting strings to LPCWSTRs. I have tryed several > methods and none work. They include: > the convert utilities A2W but that does not compile because of unknow > variables declared in the convert header file. > MultiByteToWideChar which seems to work once but not the second time i go to > use it. > The problem with all the task scheduler examples is they only show how to > work with literal (hardcoded) values for CPCWSTRs. and i can not find any > examples of how to just convert command line arguments to LPCWSTRs. > > Thanks in advance, > Fred > Fred: A2W is part of MFC/ATL so if it does not work it is because you are not using it correctly. Did you read the documentation? Likewise for MultiByteToWideChar(). Which version of VC++ are you using?
[quoted text, click to view]
ka1cqd wrote: > I have read all the info about both methods that i could find on MSDN and > used the code examples for there and could not get them to work. > > I have since found, mbstowcs() which appears to work. also it appears to > backward compatible. > > Where do i find the doucmentation on how to use the MFC/ATL?? > > How do you tell what version of the complier is being used? When i start > it, it just says visual studio .net and if i look at the versions under help > about i see a number > 69586-335-0000007-18820. > Fred: MSDN is the documentation. If you do not tell us what goes wrong, we cannot help you fix it. VC5: Visual Studio 97 VC6: Visual studio 6 VC7: Visual Studio 2002.Net VC7.1: Visual Studio 2003.Net VC8: Visual Studio 2005 It sounds as if you have VC7 or 7.1. As Jochen mentioned, the ATL conversion macros were improved as of VC7, though there is a bug (fixed in VC8) that causes them to fail when converting between UTF-8 to UTF-16 in some languages. David Wilkinson
Hi ka1cqd!
[quoted text, click to view] > I have been looking all over the place for a method to take command line > arguments and convert them to a string or wstring so i can process the data > and then covert the resulting strings to LPCWSTRs. I have tryed several > methods and none work. Why not create a unicode-app? And define the following entry: int _tmain(int argc, _TCHAR* argv[]) [quoted text, click to view] > They include: > the convert utilities A2W but that does not compile because of unknow > variables declared in the convert header file. You shouldn´t use A2W, instead use the new ATL7 macros: Cx like CA2CW -- Greetings Jochen My blog about Win32 and .NET
Hi ka1cqd!
[quoted text, click to view] > if i follow what you suggested, i need to #define _UNICODE and then > everything is in the wide format and i don't have to deal with the > conversion? Is this correct? Yes. By the way: This is the default setting for all new projects in VC2005. -- Greetings Jochen My blog about Win32 and .NET
[quoted text, click to view]
> if i follow what you suggested, i need to #define _UNICODE and then Because you use Visual Studio .NET, you can just select "Use Unicode > everything is in the wide format and i don't have to deal with the > conversion? Is this correct? Character Set" from Project Properties -> General -> Character Set. It will define both _UNICODE and UNICODE (for the CRT and Win API respectively). -- Mihai Nita [Microsoft MVP, Windows - SDK] http://www.mihai-nita.net ------------------------------------------
[quoted text, click to view]
"ka1cqd" <ka1cqd@discussions.microsoft.com> wrote in message news:65C1C63E-E877-4A6F-A36E-7B24B8363FA3@microsoft.com... >I have been looking all over the place for a method to take command line > arguments and convert them to a string or wstring so i can process the > data > and then covert the resulting strings to LPCWSTRs. I have tryed several > methods and none work. They include: > the convert utilities A2W but that does not compile because of unknow > variables declared in the convert header file. > MultiByteToWideChar which seems to work once but not the second time i go > to > use it. > The problem with all the task scheduler examples is they only show how to > work with literal (hardcoded) values for CPCWSTRs. and i can not find any > examples of how to just convert command line arguments to LPCWSTRs. If you want to keep your application ANSI, you can use GetCommandLineW() and CommandLineToArgvW(). Regards, Will
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |