Which Nsight version that can be used CUDA5.5, in VisualStudio2010? - c++

I am using CUDA5.5 at the VisualStudio2010 on Windows7 64bit.
I'm going to install a Nsight VisualStudioEdition
and I would like to debug the code of CUDA.
The Nsight3.1 that I found on the site of nVidia is like the latest version,
It had been described as corresponds to the VisualStudio2012.
Nsight3.1 work? CUDA5.5, in VisualStudio2010?
Also, is there a version of Nsight that can be used CUDA5.5, in VisualStudio2010?
Please let me know which version of nSight that can be used CUDA5.5, in VisualStudio2010?
The following message is displayed in the item of "Nsight C + + AMP Debugger" when you try to install the Nsight.
This does not it? Have failed to install?
Nsight C++ AMP Debugger
 Nsight C++ AMP Debugger for Visual Studio 2012 will not be installed.
 Requirement not met:Microsoft Visual Studio 2012 was not found.
 Nsight C++ AMP Target Support for MSVSMON will be installed
 warning:Microsoft Visual Studio 2012 MSVMON.exe was not found.

I'm using Nsight 3.1 with Visual Studio 2010 and either CUDA 5.0 or CUDA 5.5 on several systems with no problem.
Nsight is now compatible also with Visual Studio 2012, see
Install Nsight Visual Studio Edition
if local debugging (host and target on same machine) is concerned.
Concerning Nsight C++ AMP Debugger, if you do not need it, you don't have to worry about this error message. If you have Visual Studio 2010, you will be able to perform CUDA and/or graphics debugging after the installation is complete, see
getting the problem during the installation of nsight visual studio

Related

How can I set up Visual Studio 2017 to develop drivers?

According to this forum, https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/windows-wdk-on-visual-studio-2017-community/fdbd2b44-e57a-4849-903d-04001205a764
Windows Driver Kit is not currently supported by visual studio 2017.
I tried installing the Windows Driver Kit, but the test driver projects, such as this one, fail to build
https://github.com/Microsoft/Windows-driver-samples/tree/master/serial/VirtualSerial
I get this error when building:
Error MSB8020 The build tools for WindowsUserModeDriver10.0 (Platform Toolset = 'WindowsUserModeDriver10.0') cannot be found. To build using the WindowsUserModeDriver10.0 build tools, please install WindowsUserModeDriver10.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
I already tried retargeting the Solution to the two options I have: 10.0.17134.0 and 8.1, but the same error keeps coming up.
What do I need to do to build this sample driver? Do I need to install VS2015? VS2017 community edition? Why isn't this WDK supported by the Visual Studio 2017 professional version?
Thanks,
Visual Studio 2017 definitely supports kernel-mode device driver development; there's no doubt about that because I've been using VS17 for it for many, many months.
Use the latest version of Windows Driver Kit (WDK) which can be downloaded and installed from MSDN: https://learn.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
Furthermore, you can always use the Enterprise WDK and then you can simply build using that if you wanted to from command-line. (Also can be found on page linked-to above)
Download the correct WDK installer for your edition of Visual Studio 2017:
WDK for Windows 10, version 1809 for Visual Studio Community 2017
WDK for Windows 10, version 1803 for Visual Studio Professional 2017
WDK for Windows 10, version 1709 for Visual Studio Enterprise 2017
Visit https://learn.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads for more information.
Not exactly a solution, but Windows 8.1 WDK works with Visual Studio 2017 Enterprise,
Download it from here, just need to retarget the project to 8.1
https://www.microsoft.com/en-us/download/confirmation.aspx?id=42273
In addition, I needed to get VS2015 C++ Build Tool to fix a missing Microsoft.cpp.props error
http://download.microsoft.com/download/5/F/7/5F7ACAEB-8363-451F-9425-68A90F98B238/visualcppbuildtools_full.exe
Developing drivers to windows is quite interesting one will be exposed to advanced Operating System Concepts.The set up for the environment will be IDE
IDE - Visual Studio (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16)
Compilers (WDK)
Debugger (WDK)
WDK contains both(https://go.microsoft.com/fwlink/?linkid=2085767). Latest Visual Studio(VS2019) will come along with the latest WDK(10, 1903 as of now).
Sometimes plugins might not work properly i.e integration issues between Visual Studio and WDk.
By going to the location "C:\Program Files (x86)\Windows Kits\10\Vsix\VS2019" and run VSIX installer.
Now in a new project, driver related templates are available.

Remote debugging on Surface Pro 3

I've installed x64 version of remote debugging components for Visual Studio 2015 on my Surface Pro 3 with Intel Core i3 CPU and recently updated to Windows 10 Pro Insider Preview x64.
When I'm trying to debug remotely simple universal application from Visual Studio 2015 RC (development machine runs Windows 8.1 Pro) I'm having this error in the output window:
Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named '192.168.1.2:4020 (hosthame)'. The remote debugger is older than this version of Visual Studio 2015 RC, and Visual Studio is no longer compatible with it. Please upgrade your remote debugger to match Visual Studio.
Also there are records of failed attempt to connect in the main (log) window of Remote Debugging Monitor.
So, is there any "more updated" version of remove debugger component for Visual Studio 2015 RC then the current one I'm using, which, btw, has version 14.0.22310.1 and was "built by: DP" (have no idea what does it mean)?
Or any thoughts about other ways to workaround this issue?
I'm looking into installing Visual Studio on the Surface directly, but would like to avoid it if possible.
OK, I'll google next time harder - Remote Tools for Visual Studio 2015 RC (this link is no longer available, please use the links bellow).
Update (2016-06-28)
Remote Tools for Visual Studio 2015 Update 3:
Download (this link is no longer available, please use the links bellow)
Update (2016-09-28)
x64 - Remote Tools for Visual Studio 2015 Update 3
x86 - Remote Tools for Visual Studio 2015 Update 3
ARM - Remote Tools for Visual Studio 2015
Sevenate, your latest link is for the 2013 and not the 2015. Your second link still works, people just have to go to:
Tools for Visual Studio 2015->Remote Tools for Visual Studio 2015 and download the one for Update 3. I hope this helps

Which XP version does Visual Studio 2012 supports [As Target OS]

Which version of windows XP does Visual Studio 2012 supports.
[Edit: Which version does VS12 supports compiling to]
I found this article:
http://blogs.msdn.com/b/vcblog/archive/2012/10/08/windows-xp-targeting-with-c-in-visual-studio-2012.aspx
That states that it supports XP SP3. But I didn't find any information for VS12 update 4.
Also, If the code I compile using VS12 doesn't crush on XP SP2 and seems to work.
Is it safe to use it? why not?
Thanks
It's correct, Visual Studio 2012 can compile binaries compatible with Windows XP SP3.
You need to install the Platform Toolset v110_xp and select it in the general configuration properties of your project.
If "safe" means that it works the answere is yes. We have 12.000 installations of our software compiled with Visual Studio 2012 (and recently Visual Studio 2013) perfectly working on Windows XP SP3.
The only big problem is run time debugging: you can't install Visual Studio 2012 on Windows XP so it could be a problem to find bugs that accidentally happens only on Windows XP.

CUDA does not work on Visual Studio 2013 - toolkits 4.2, 5.5 and 6

I understand that Cuda 6 does not work with Visual Studio 2013. But shouldn't Cuda 5.5. or Cuda 4.2 work with Visual Studio 2013?
I have Cuda 4.2, 5.5 and 6 installed. If I right click on VS project, and select Build Customizations option, I only see Cuda 6 listed. For Cuda 6, it tells me that I must choose the older v11 toolset, and the other two toolkits are simply non existent.
Is there any way to get Cuda to work on VS 2013?
The supported visual studio versions are listed in the windows getting started guide or toolkit release notes for each CUDA toolkit release.
The CUDA 6 getting started guide is here.
The only toolkit that officially has support for VS 2013 at this time is CUDA 6.5RC available for download to registered developers.

Hello World C++ CUDA Program in Visual Studio 2010 (Windows 7)

I am trying to compile this Hello World program in Windows 7 with Visual Studio 2010 installed, but I get the following error message when I run nvcc hellocuda.cu:
nvcc fatal : nvcc cannot find a supported cl version. Only MSVC 8.0 and MSVC 9.0 are supported
How can I compile this CUDA program ?
NVCC checks VC++ compiler version from Visual Studio environment variables. NVCC says it supports only MSVC 8.0 and 9.0 compilers. In your case, you have MSVC 10.0 compiler. There seems to be a workaround to this issue, check out post #7 in this thread:
http://forums.nvidia.com/index.php?showtopic=179531 and also
http://forums.nvidia.com/index.php?showtopic=88585
If you keep having problems getting it working with MSVC10, bear in mind that you can download the Express version of MSVC9 (i.e. the 2008 version) for free -- so you can always download it and compile with that instead. But I would try swatkat's workaround first :)
Here's the link:
http://www.microsoft.com/express/Downloads/
Visual Studio 2008 Express was needed. (Thanks sgolodetz)
So with Visual Studio 2010 Professional (maybe 2010 Express works too?), NVIDIA Parallel Nsight, CUDA Toolkit, Developer Drivers, and GPU Computing SDK code samples (toolkit, drivers, and sdk can be downloaded here) I was able to run the example Hello World in CUDA program.
How to create/upgrade a CUDA project in VS2008 and VS2010 to work with Nsight 1.5 and CUDA 3.2 was very helpful in starting a new VS 2010 CUDA project with the proper settings.
Side note: I was never able to get the command line nvcc to work correctly, but I rather use VS 2010 IDE instead.
Update: How do I start a new CUDA app in visual studio 2008?'s answer was also useful
With CUDA 4.0 you can use the VC10 toolchain. See this answer for a step-by-step.