I just updated my compiler to VS2015 after using VS2005 for many years. I built a small test app and linked it to my DLLs (which are still built with the older compiler). Ultimately, they'll be getting built with the new compiler and I was aware of some things to avoid (such as not allocating memory in a DLL and trying to release it in the new app etc). But I didn't anticipate the problem with std::string. Consider this example:-
void some_func()
{
std::string test = Glib::get_application_name();
}
'test' is a std::string in the format expected by VS2015 - whereas (in my case) the call to 'get_application_name()' returns a std::string in the format that was known to VS2005 - so calling that function from my new app is guaranteed to crash my program. I figured that if I could obtain the application name in a POD char array, that might help - and I quickly discovered that this change seemed fix things:-
std::string test = Glib::get_application_name().c_str();
but when I mentioned it on a popular programming forum, someone pointed out that if the above was working, that was purely a case of luck.