I vaguely remember that you could just use CString by itself, and it appears 
that you can!

Re: C++ String: How to use 'CString' in non-MFC applications?
Starting VS 2003, you can use CString in non-MFC applications by including 
header atlstr.h:
Code:
#include <atlstr.h>
A sample console application with CString:
Code:
#include <atlstr.h>
#include <iostream>

int main ()
{
CString strTest (_T("This is a CString in a console application!"));
 
#ifdef UNICODE
   std::wcout << (LPCTSTR)strTest;
#else
   std::cout << (LPCTSTR)strTest;
#endif
 
return 0;
}
You can also use CStringA as a ANSI string class, and CStringW as a 
wide-character string class.


With this solution there’s no need to make the linker work hard at throwing out 
code you’re not using.

-Barry


On Mar 7, 2014, at 12:56 PM, Steve-Ogilvie <steven.ogil...@titus.com> wrote:

> Off topic 
> 
> Is it a big deal if I statically link MFC with the burn solution? 
> I am using CString string methods in the BA Extension DLL (not all of WIX
> just the Burn.sln) 
> 
> Steve 
> 
> 
> 
> 
> --
> View this message in context: 
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Solution-tp7593201.html
> Sent from the wix-devs mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works. 
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to