I've been using version 1.1.3 and see there is now a newer version with NuGet support. I just did a test with that.
Can I somehow check if the MSBuild task that does all the magic is
actually run or not?
You can get more detail from MSBuild using the command line or adjust the verbosity that Visual Studio requests: Tools > Options > Project and Solutions > Build and Run > MSBuild project build output verbosity [VS 2010]. You'll probably want to reset it as soon as you are done troubleshooting.
I saw the target and task were being called but didn't see any results until I switched the project platform to x86. Then I see various, relevant log entries including Adding .vtentry:0 .export....
What should the project file contain (it seems to be suspiciously empty to me?)
There isn't much needed in the project file. NuGet does it all: A reference to the DllExport assembly and an include for the target file.
A couple things that I can think of that might be tripping you up:
- Make sure you are actually building the project. The Solution Build Manager can have some projects not set to build for the selected solution configuration.
- Make sure you are checking the right DLL. The build task writes the path into the build log. The line starts with
Assembling.
