I started off with the release candidates of the CUDA 4.0 toolkit and Parallel Nsight 2.0. Then when they went into production release, I uninstalled all my NVIDIA tools and installed the production releases of the CUDA Toolkit 4.0 and Parallel Nsight 2.0. When I tried creating a new CUDA project I followed the steps on Ade Millers blog. First setting my configuration to x64. Then this is where things always go downhill. When you highlight the project in the Solution Explorer tab and then go to Project->Build Customizations and select 4.0, Visual Studio behaves very strangely. First off, when I right click the .cu file and click Properties to select its “Item Type” as CUDA C/C++ I instead have the properties tab open?!? Then when I close the project and try to reopen it I get an error message that reads, “The result “” of evaluating the value “$(CudaBuildTasksPath)” of the “AssemblyFile” attribute in element is not valid. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\CUDA 4.0.targets”. I’ve actually found a very strange workaround to fixing my project. Apparently if I delete the VC++ Project Filter File, load the project, and clean it, it will work. Yes, I am talking about the file responsible for separating the Source Files filter from the Header Files filter. However, this will only work on my previous CUDA program solutions. I cannot do this to new projects. To actually create a new project I click New Project->NVIDIA->CUDA 4.0 Runtime and set things up as usual. If you’re reading this right now you’re probably thinking why don’t I just do the workaround? The answer is that I have a few parallel programming applications on the CPU that I want to extend to use CUDA and I don’t to risk ruining them. If anyway has questions or insight about this a I’d appreciate a reply.
I’ve attached an example of a project that won’t work.
Example.zip (20.6 KB)