It should be. There isn’t a limitation on what can be compiled, only what’s
available with Express by default. If you supply the code, it will compile it.
-Barry
On Mar 8, 2014, at 11:27 PM, Blair Murri <os...@live.com> wrote:
> Can that still be compiled using Visual Studio Express?
>
> Sent from my Windows Phone
> From: Steve-Ogilvie
> Sent: 3/7/2014 4:36 PM
> To: wix-devs@lists.sourceforge.net
> Subject: Re: [WiX-devs] Burn Solution [P]
>
> Classification: Public
>
> Thanks Barry,
>
>
> I included:
>
> #include <cstringt.h>
>
> #include <atlstr.h>
>
>
> Thanks,
>
>
> Steve
>
>
>
>
>
> This message has been marked as Public by Steven Ogilvie on March-07-14
> 7:27:14 PM.
>
> The above classification labels were added to the message by TITUS Message
> Classification.
> For more information visit www.titus.com.
>
>
> From: Barry Nolte [via Windows Installer XML (WiX) toolset]
> [mailto:ml-node+[hidden email]]
> Sent: March-07-14 6:40 PM
> To: Steven Ogilvie
> Subject: Re: Burn Solution
>
>
> 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 <[hidden email]> 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
> [hidden email]
> 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
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Solution-tp7593201p7593210.html
>
> To unsubscribe from Burn Solution, click here.
> NAML
>
>
> View this message in context: RE: Burn Solution [P]
> Sent from the wix-devs mailing list archive at Nabble.com.
> <Mail Attachment.txt><Mail
> Attachment.txt>------------------------------------------------------------------------------
> 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
