How Can I Set An Entrypoint For DLLs ? [Solved]

[T0P-CENT]

First i thought entry point in dlls was DLLMain but then when i try to import it in C# i get an error that entrypoint wasn't found

here is my code

#include <Windows.h>

int Test(int x,int y)
{
return x+y;
}

BOOL APIENTRY DllMain( HMODULE hModule,
                       DWORD  ul_reason_for_call,
                       LPVOID lpReserved
					 )
{
	switch (ul_reason_for_call)
	{
	case DLL_PROCESS_ATTACH:
		MessageBox(0,L"Test",L"From unmanaged dll",0);
	case DLL_THREAD_ATTACH:
	case DLL_THREAD_DETACH:
	case DLL_PROCESS_DETACH:
		break;
	}
	return TRUE;
}

And if you dont mind can you give me little explanation about entry point ?
Like do i have to set import the same dllagain and changing the entry point so i can use other functions? thanks in advance

[Nico]

Youre exporting DLLMain?

[T0P-CENT]

Youre exporting DLLMain?

Nope , but i got my problem solved thanks
solution : before any function/void

extern "C" __declspec(dllexport)

[Hassan]

Naice.

A nigga mad. Opened again.
@Jason: Soothe your pain now.

[Jason]

Just to clarify, even when exporting with the

extern "C" __declspec(dllexport) keyword, name mangling can still occur. There is, however, an easy way to find out what name your exported function was given when it was exported. All exported functions are added to the PE image file's "export table". So using any PE explorer you can simply go to the export table and see what functions your dll exports, and what names they have.

[freedompeace]

Just to clarify, even when exporting with the

extern "C" __declspec(dllexport) keyword, name mangling can still occur. There is, however, an easy way to find out what name your exported function was given when it was exported. All exported functions are added to the PE image file's "export table". So using any PE explorer you can simply go to the export table and see what functions your dll exports, and what names they have.

Linking using C linkage (extern C) disables name mangling for the specified declaration -- C doesn't mangle names; C++ does. :)

It also happens to be that C and C++ (as in extern "C" and extern "C++") are the only supported string literals for the extern keyword in MSVC.

[Jason]

Linking using C linkage (extern C) disables name mangling for the specified declaration -- C doesn't mangle names; C++ does.

It also happens to be that C and C++ (as in extern "C" and extern "C++") are the only supported string literals for the extern keyword in MSVC.

Weird, exported my function with the extern "C" specifier and looky here, it was exported as _function@14

Maybe this was just a one off