<p>I’m generally more of a grep person but sometimes it’s easier to just use the built-in search in Visual Studio, especially if you want to be able to restrict the search to parts of your Visual Studio solution. Visual Studio does have pretty powerful search built in if you do use regular expressions instead of the default text matching. Here are a couple of regexes to get you started:</p>

<p>Visual Studio 2013, much like its predecessor Visual Studio 2012, also “features” the SHOUTY uppercase menus. Like in Visual Studio 2012, these can be <a href="http://blogs.msdn.com/b/zainnab/archive/2013/08/21/visual-studio-2013-turn-off-the-uppercase-menu.aspx">turned off using a registry setting</a>.</p>

<p>As VS2012’s C++ compiler doesn’t support “true” variadic templates, the new runtime library classes that use variadic templates are implemented using macro magic behind the scenes. In order to get the “variadic” templates to accept more than the default of five parameters, you’ll have to set _VARIADIC_MAX to the desired maximum number of parameters (between five and ten).</p>

<p>After all the brouhaha over Visual Studio 2012 not being able to build executables for Windows XP, it looks like Microsoft has reconsidered:</p>

<p>… make sure that you have removed all dependencies on the project that you are about to remove before you remove the project from the solution.</p>

<p>Try stopping mspdbsrv.exe (the process that generates the pdb files during a build) if it is still running. My understanding is that it’s supposed to shut down at the end of the compilation but it seems that it can turn into a zombie process and if the latter happens, you can get the above error when linking your binaries.</p>