I believe most of the points regarding the causes and remedies have been covered by all contributors in this thread. I just want to point out for my 'unresolved external' problem, it was caused by a datatype defined as macro that gets substituted differently than expected, which results in that incorrect type being supplied to the function in question, and since the function with type is never defined, it couldn't have been resolved. In particular, under C/C++ -> Language, there is an attribute called 'Treat WChar_t As Built in Type, which should have been defined as 'No (/Zc:wchar_t-)' but did not in my case.

在我的情况下，我有多个名称空间在我的头文件中没有嵌套(一个接一个)，但在我的源文件中，我不小心嵌套了一个名称空间在另一个:

// myExample.h

#ifndef MYEXAMPLE_H
#define MYEXAMPLE_H

namespace A
{
  void aFunc();
}

namespace B
{
  void bFunc();
}

// myExample.cpp

#include "myExample.h"

namespace A
{
  void aFunc()
  {
    ...
  }

  namespace B   // whoops! I nested this inside namespace A when I didn't mean to.
  {
    void bFunc()
    {
      ...
    }
  }
}

// main.cpp

#include "myExample.h"

int main()
{
  myExample::B::bFunc();
  
  return 0;
}

当我在Main中使用F12对函数“Go to definition”时，Visual Studio在源文件中找到了代码，尽管它是在一个更深层的命名空间中声明的。

调试技术

我在尝试调试问题时重命名函数时发现了这个问题。重命名预览窗口显示了一个“External References”节点，其中源文件中的函数意外地嵌套在另一个名称空间下。

I believe most of the points regarding the causes and remedies have been covered by all contributors in this thread. I just want to point out for my 'unresolved external' problem, it was caused by a datatype defined as macro that gets substituted differently than expected, which results in that incorrect type being supplied to the function in question, and since the function with type is never defined, it couldn't have been resolved. In particular, under C/C++ -> Language, there is an attribute called 'Treat WChar_t As Built in Type, which should have been defined as 'No (/Zc:wchar_t-)' but did not in my case.

请参阅MSDN上的链接器工具错误LNK2019，它有导致LNK2019的常见问题的详细列表。

导致“未解析的外部符号”错误的一个可能原因是函数调用约定。

确保所有源文件都使用相同的标准(.c或.cpp)，或者指定调用约定。

否则，如果一个文件是C文件(source.c)，另一个文件是.cpp文件，并且它们链接到相同的头文件，那么将抛出“未解析的外部符号”错误，因为该函数首先被定义为C cdecl函数，但随后使用相同头文件的c++文件将寻找c++函数。

为了避免“未解析的外部符号错误”，请确保函数调用约定在使用它的文件中保持相同。

我也有同样的问题。在我取出最新的代码后，我的程序一天还能工作，第二天就不行了。

最新的代码不包括我在库中引用的项目。所以当我重建我的库时，它删除了。obj文件，whoopsy.....

我重新包含了我需要的项目，建立了我的库，然后重建了我的失败的项目，它运行得很好。

这个故事的寓意是，在深入到兔子洞之前，验证你的.obj文件是你引用它的地方。