This project references NuGet package(s) that are missing on this computer

In my case, I had to remove the following from the .csproj file: In fact, in this snippet you can see where the error message is coming from. I was converting from MSBuild-Integrated Package Restore to Automatic Package Restore (http://docs.nuget.org/docs/workflows/migrating-to-automatic-package-restore)

Error “system” is ambiguous?

You need to #include <cstdlib> Source: http://en.cppreference.com/w/cpp/utility/program/system Also, try to avoid system, it’s dangerous. To pause the program when it’s finished, put a breakpoint on the } at the end of main. There isn’t a standard way to clear the screen unfortunately. For future reference, the red squiggles are intellisense errors, which are shown by a different front-end than the one that … Read more

Already defined in .obj – no double inclusions

This is not a compiler error: the error is coming from the linker. After compilation, the linker will merge the object files resulting from the compilation of each of your translation units (.cpp files). The linker finds out that you have the same symbol defined multiple times in different translation units, and complains about it … Read more

General way of solving Error: Stack around the variable ‘x’ was corrupted

Is there a general way to debug this error with VS2010? No, there isn’t. What you have done is to somehow invoke undefined behavior. The reason these behaviors are undefined is that the general case is very hard to detect/diagnose. Sometimes it is provably impossible to do so. There are however, a somewhat smallish number … Read more

Visual C++ executable and missing MSVCR100d.dll

You definitely should not need the debug version of the CRT if you’re compiling in “release” mode. You can tell they’re the debug versions of the DLLs because they end with a d. More to the point, the debug version is not redistributable, so it’s not as simple as “packaging” it with your executable, or zipping up those … Read more