CUDA Toolkit 5 Production Release and Visual Studio 2010 Integration

Question

In the absence of the NVidia CUDA forum, does anyone know how to fix this? It seems that the VS integration of the CUDA toolkit is having problems.

I just installed the release version of the CUDA toolkit 5 (32-bit for laptops in Windows 7), replacing the release candidate (which worked fine), and now I can not compile or build anything, including CUDA samples.

Everything I tried gives an error, for example: ... BuildCustomizations \ CUDA 5.0.targets (360.9): error MSB4062: The task "Nvda.Build.CudaTasks.ResolvePaths" cannot be loaded from the C: \ Program Files assembly (x86) \ MSBuild \ Microsoft.Cpp \ v4.0 \ BuildCustomizations \ Nvda.Build.CudaTasks.v5.0.dll, make sure the declaration is correct, that the assembly and all its dependencies are accessible, and that the task contains an open class that implements Microsoft.Build.Framework.ITask.

The "CUDA 5.0.targets" file (this is an XML file) contains several UseTask elements, and I don’t see a link to the mentioned ITask class, but I don’t want to start editing a file that I don’t understand.

A similar error is given for CUDA 4.2 if I switch Build Customisations.

This is using Visual Studio 2010 Professional. Non-CUDA projects are still compiling and building.

Any suggestions on where to start?

Answer 1

To fix, you need to install the 64-bit CUDA 5.0.32 SDK (latest version of CUDA 5.0). It contains a newer version of Nvda.Build.CudaTasks.v5.0.dll than the 32-bit installer (date modified 09/25/2012, not May 2012).

I could not copy the Dll to the right place because it was used by another process. To get around this, I used a batch file made using Windows SAFE_MODE with a CMD prompt (use F8 at boot time to select the option to start in safe mode).

Command command (working on my 64-bit Windows system): copy "[YOUR INSTALLATION WAY] \ CUDA \ v5.0 \ extras \ visual_studio_integration \ MSBuildExtensions \ Nvda.Build.CudaTasks.v5.0.dll" "C: \ Program Files (x86) \ MSBuild \ Microsoft.Cpp \ v4. 0 \ BuildCustomizations "

Make sure your details and goals are also copied from the SDK installation folder.

Answer 2

This problem probably occurs because the Microsoft .NET Framework features are disabled.

I answered another question, which is the same as yours.

fooobar.com/questions/1423481 / ...