We have created a Visual Studio macro that will reload the .sln solution file in order to avoid clicking "Reload" in multiple dialogs. It currently works with Visual Studio 8 2005 (and probably with VS 9 2008, also, but not yet tested in that environment.)
<br><br>The macro is called automatically by CMake only when necessary and will prompt the developer only when a .sln file or .vcproj file has changed.<br><br>Try out the nightly Windows CMake installer found here to see if it solves the problem for you:
<br><a href="http://www.cmake.org/files/vCVS/cmake-2.5.20071126-win32-x86.exe">http://www.cmake.org/files/vCVS/cmake-2.5.20071126-win32-x86.exe</a><br><br>Please reply here to the CMake mailing list with additional comments or problem reports.
<br><br><br>Thanks,<br>David Cole<br>Kitware, Inc.<br><br><br><div><span class="gmail_quote">On 8/28/07, <b class="gmail_sendername">KSpam</b> <<a href="mailto:keesling_spam@cox.net">keesling_spam@cox.net</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">One major annoyance that users have with CMake integration in VisualStudio is<br>having to click "Yes" to reload the project files after CMake regenerates
<br>them. There is no "Yes to All" option. With hundreds of projects, it takes<br>a while to click all of the "Yes" buttons.<br><br>Does anyone know if there is a way to force the reload in Visual Studio, so
<br>that the user is not bothered with the dialog boxes? Is there a<br>configuration option in Visual Studio?<br><br>I tell the users to exit Visual Studio, reconfigure CMake, and then reopen<br>Visual Studio, but that is a suboptimal solution.
<br><br>Thanks,<br>Justin<br>_______________________________________________<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake
</a><br></blockquote></div><br>