Comments on JTB World Blog: Solution to registering of DLL problem on 64-bit s...

Owen, it seems like your case is different as I ha...

2009-10-11T10:45:18.021-04:00

Owen, it seems like your case is different as I had no problem to build the MSI. It is first when running the MSI i get the problem (details found in the MSI log file).

I had already tried this and other permutations in...

2009-10-11T10:34:35.971-04:00

I had already tried this and other permutations in the past, but when I read your post I tried exactly what you suggested with one of my projects, but I still got the same warning.

Perhaps my case is slightly different (I get "WARNING: Entry point 'MyExportedFunction' not found in module 'MyModule' for custom action 'MyCustomAction'." when building). I am using Visual Studio 2008.

If you were able to get the forcibly renamed function working without warnings, I may need to look more closely at why it failed for me.

Owen, thanks for your comment, as far as I have fo...

2009-10-11T01:31:40.053-04:00

Owen, thanks for your comment, as far as I have found in my tests it works either way. Using Export makes both the MSI working as expected and I have not found any problems with the program either.

What problem do you think this might introduce?

I guess I could use WiRunSql.vbs to update the MSI postbuild too instead of manually update it but not sure if it is a better idea or not.

Are you sure this works the way you think? The inc...

2009-10-10T18:50:10.168-04:00

Are you sure this works the way you think? The incorrect name decoration is introduced when building the MSI, not when linking the module that exports the functions. The only way I've ever been able to resolve this bug is to ignore the build warning, then run a postbuild script to correct the name in the MSI database.