Home/ Questions/Q 8550971
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T14:05:21+00:00

I am attempting to create a CLI DLL to bridge between my unmanaged C++

  • 0

I am attempting to create a CLI DLL to bridge between my unmanaged C++ executable project and another managed project, all in a single Visual Studio solution.

The problem I am having is earlier, though: I am unable to link reference the unmanaged C++ project in my new CLI project. I have included the required .h files, and added a reference to the unmanaged project in the CLI project. The compilation is successful, but I am getting linkage errors I have not seen before:

Error 2
error LNK2028: unresolved token (0A000088) “public: __cdecl …

I have added a reference in the project properties and included the .h files.

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Seems like the linker is missing some intermediate information on the other project. I truly don’t remember if ‘referencing’ native projects does set up the linking phase automatically.. I actually find it strange you say “reference”.. for me the word “reference” it a bit limited to the world of .Net assemblies because of the “add reference” in the VS, which makes noone care about includes/libraries and which IIRC is unavailable for native dlls for obvious reasons. If you meant you configured the linker options manually, then pardon me 🙂

    If not – please explain how did you reference the native module.

    Either way, if the “referencing” worked earlier, the file names might went out of sync if i.e. you renamed the project, of maybe file timestamps were a bit off and the VS did not notice new versions.. Simple Clear&Rebuild sometimes magically helps. If not, you can try to manually delete Debug/Release/Bin/Obj folders and try rebuilding again.

    To try at diagnosing, the first step is to see what the linker is given as input: in the project property pages for the C++/CLI project, check Linker->CommandLine and see if a file with name similar to “myOtherNativeCppProjectName.lib” is visible there. If not – here’s the problem, just add it in the linker options on previos linker pages, or re-do the reference-adding, then clean, rebuild and see what happens.

    To say something more, you’d have to post whole error message – this one is truncated at function name, so it’s hard to tell if it is your function, or some missing-library module. As the compilation phase succeeded and the problem is at link – are you 100% sure you have that function implemented? I mean, correct .h was surely provided to the C++/CLI project, but were the right .cpp files matching the .h file included in the native? That’s quite common too to forget to add one file. Or forget to instantiate a template.. Or mistype class/function names between .H and .CPP..

    • 0