I already installed VS 2017 Community in my PC and when I run it, it wont start at all and will only beep an error sound. What could be the problem on this?
Thank you.
Related
I have all these packages because I have had in my PC a previous version from Visual Studio. But I have to install Visual Studio 2016. My question is: will it have any problem trying to run in the future although I have these things?.
Thank you!
I upgraded VS from VS 2017 RC to VS 2017 and I have noticed that when I try to start it up that it just makes the Windows Ding sound and nothing happens.
I would uninstall Visual Studio with the visual studio uninstaller on github and then reinstall.
Sounds like the upgrade did not work right
https://github.com/Microsoft/VisualStudioUninstaller
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
I want to experiment with usb drivers on c++. I'm using visual studio express 2013 and I could not find WinUSB template. I have seen this guide. However it is for visual studio ultimate/pro 2012. Can anyone help me?
Thanks in advance!
According to this page
For building Windows 10 driver samples, Visual Studio Community 2015 works with WDK 10 to build samples from the samples gallery. Visual Studio Community 2015 is available free.
This contradicts some other pages (e.g. this one) which say you need Visual Studio Professional or Ultimate. But it is wrong - I just downloaded VS 2015 Community, and the Windows Driver Kit, and it installed fine and has a WinUSB sample.
I'm using Microsoft Visual Studio 2010. It was going fine until this morning when I try to build my code. It gave me this weird error:
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms
\Win32\Microsoft.Cpp.Win32.Targets(147,5)
:error` MSB6006: "CL.exe" exited with code 1073741855.
I have no idea why this error is occuring. I need help please.
I am using Window 7.
1073741855 is 0x0x4000001f, and 0x1f is decimal 31, and 31 is ERROR_GEN_FAILURE. In other words, something is hosed and VS isn't going to tell you what it is.
Go to Control Panel/Programs and Features, right click, Uninstall/Change, Repair/Reinstall. If that doesn't fix the problem, I would uninstall VS completely and reinstall.
For those of you looking to avoid the (timely) process of uninstalling and reinstalling Visual Studio, a simple restart worked for me. I have noticed this happens more often when I have multiple Visual Studio windows open.