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
Related
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.
I inherited a project that was created in Visual Studio 2015 with SQL Server Data Tools version 14.
I'm running VS 2017 version 15.6.0 with SQL Server Data Tools 15.1.61801.210
When I try to open the solution it just fails with the below error message. What do I need to do in order to "upgrade" the solution so I can work with it?
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR\LabSOR.dtproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR.sln"
Ended up the SSDT integration elements hadn't installed. Once I did that I could right-click on the project in the solution explorer and reload it, and then it started working.
I am trying to install SSDT for VS 2017 (15.5.1), and I get this error:
"The requested metafile operation is not support (0x800707D3)".
The Microsoft page states that this was fixed in the current release but apparently that isn't true. From Microsoft's change log: Fix an issue where setup fails with the following error message:
"The requested metafile operation is not support (0x800707D3)".
I have Visual 2017 installed and working and all updates to it have been installed
I am running Windows 7 Enterprise (company machine out of my control)
Has anyone figured out a work around?
https://learn.microsoft.com/en-us/sql/ssdt/changelog-for-sql-server-data-tools-ssdt
The method I successfully used after encountering the failure message cited above was to uninstall the Visual Studio 2015 shell using add / remove programs (Win 10 Pro); rebooting, and then reinstalling SSDT for Visual Studio 2017 (Community Ed).
I am not sure how the Visual Studio 2015 Shell got installed: I previously removed all prior versions of SQL Server, and Visual Studio from the machine. I did build out the machine again by first installing SQL Server 2017 Dev, Visual Studio 2017 Comm Ed.
Same issue, Windows 10 Ent. Ended up installing SSDT for VS2015.
Visual Studio 2015u3 is serviced by cumulative updates with KB3165756, which contains, among other things, fixes to the C++ compiler and libraries.
However KB3165756 refuses to do anything on a computer where Visual C++ Build Tools 2015 Update 3 is installed. It really wants one of VS Pro, Enterprise, Community or Express.
Are there special patches for Visual C++ Build Tools, or is it not updated at all and so it is actually a better idea to switch to Visual Studio Express 2015 for Desktop, in order to be able to receive patches?
Here is the answer I got on MSDN Visual Studio Development > Visual Studio Setup and Installation forum:
However KB3165756 refuses to do anything on a computer where Visual C++ Build Tools 2015 Update 3 is installed. It really wants one of VS Pro, Enterprise, Community or Express.
It is reasonable, check this: https://msdn.microsoft.com/en-us/library/mt752379.aspx and it describes this update is applies to
Visual Studio Professional 2015
Visual Studio Enterprise 2015
Visual Studio Community 2015
Visual Studio Express 2015 for Web
Visual Studio Express 2015 for Desktop
Visual Studio Express 2015 for Windows 10
I have researched around and it looks like there is no special update for the Visual C++ Build Tools 2015, and refer to this blog: https://blogs.msdn.microsoft.com/vcblog/2015/11/02/announcing-visual-c-build-tools-2015-standalone-c-tools-for-build-environments/
The latest release of the Visual C++ Build Tools 2015 is here: Download Visual C++ Build Tools 2015
If you still want to install, it looks like you need a VS 2015 RTM update version on your computer. Since the VS community 2015 with update 2 and Visual Studio Express version are free and you can think about it.
Best regards,
Sara
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