I figured out what the problem was:
When building a mexw32 with IDE (Visual Studio), Module Definition file (.def) is required. When I wrote the def file, I named the library as 'myfunction'
LIBRARY myfunction
EXPORTS mexFunction
However, the mexw32 file name was not 'myfunction'. After I named the mexw32 file same as the name specified in def file, I can correctly evoke the function in Matlab.
The reason why I wanted to use Visual Studio for building mexw32 is that I can deal with a single interface to build the binary. Of course, mex -O -c code.cpp is not too difficult, but managing projects having dependencies to multiple libraries is quickly becoming a complex task. For that task, Visual Studio is a good tool.
Thanks for participating for the issue!
