With these it helps The linker doesn't know about overloading (it has to be generic for multiple languages). All it knows about are symbols that it needs to resolve. The compilers name-mangling creates two different symbols for the two function overloads, allowing the linker to resolve them to the correct function.
Any of those help The _ZN13KeypathHelper11getCacheObjEv symbol is a mangled name for KeypathHelper::getCacheObj() (you can easily translate using c++filt, for example). Given that you have only added a method and whatever is loading the shared object cannot find it makes me think that you either haven't updated the shared object or forgot to provide a definition for KeypathHelper::getCacheObj() (in other words — implement the method). In order to investigate, you have to see what is failing to resolve the symbol. Usually, developers have a sense for it. Say, if a binary XXX cannot load library YYY due to unresolved symbol, then XXX is using it and it does not appear to be in YYY (or anywhere else for that matter). If there is no sense for that, one can resort to reading ld.so (8) manual page and debug the dynamic linker by using available means like defining LD_DEBUG.
ASP Identity GenerateUserTokenAsync(string purpose, TKey userId) purpose options
I hope this helps . You seem to be expecting global symbols to have an underscore prepended to them. This is something that isn't done in ELF which is the object format that linux uses. Older binary formats like a.out or coff required that, ELF doesn't. Btw. the term "mangling" is usually used for C++ symbol mangling which is a different thing.
What is the purpose of VSTS dot net core build task version 2 purpose
it should still fix some issue .NET Core BUild task (dotnet build) only build the specified project and it's dependencies. It not provide converting .ts to .js and js.map (you can refer TypeScript). More detail about dotnet build, you can refer dotnet-build.