DISCLAIMER: Yes, I do realize MFC is pretty trash and that I should avoid it at all costs. However, as of the moment, I'm stuck in a MFC project that I'm trying to integrate with JUCE to start migrating away from MFC - eventually we'll move everything to JUCE.
I created a JUCE project with a few customized controls (Sliding Panel Component, Image buttons, SVG resources, a TableListBox.. nothing too crazy) and exported it to VS2013. Everything compiles, runs, works, etc. which is perfect. However, when I choose to include MFC in a shared DLL, the project generates 67 errors, all of which are unresolved symbols. There were a few threads already on the forum with this same problem discussed (http://www.juce.com/forum/topic/jucequake-use-mfc-static-library-unresolved-symbols) but no true solution as to what is occurring. Suggested in the previous threads were to toy with the VS2013 project settings to try and get rid of the errors but so far, no luck.
Is there any information on just doing the above? Taking a JUCE project that compiles fine and just telling it to use MFC in a shared DLL? I get the same errors whether I choose static or shared, which is strange, since my project itself doesn't utilize any MFC at all, yet. Just the act of attaching MFC on causes the errors. I have cleared the project via VS2013, changed settings, etc.