I have Visual Studio 2017, Community edition; whenever I start my computer, I recieve from it four warning messages of missing files: extension.vsxmanifest, Nvda.UnifiedDebugger.Package.pkgdef, Nvda.Vsip.Debugger.Device.dll.pkgdef and Nvda.Vsip.Net.dll.pkgdef.
I get that there is some problem with some NVIDIA packages (I recently installed the CUDA Toolkit), but how can I solve it?
Try to open the visual studio with administrator privillage (Run As Administrator) for one time after CUDA toolkit installation (this worked for me).
Related
"Setup Failed" Recursion too deep; stack overflowed 0x800703E9.
I have windows 10 and newest visual studio version. I have tried rebooting to make sure I have as many resources as possible. I have 4g ram.
If the SSDT installer gives you multiple instances of Visual Studio to choose from, try the "new" option.
I ran into this problem trying to install SSDT 15.8.1 on Windows Server 2012 R2 with the latest version of Visual Studio 2017 (v15.8.6) already installed. The SSDT installer gave me 2 options in a dropdown box.
Install tools to this Visual Studio 2017 instance:
Visual Studio 2017
Install new SQL Server Data Tools for Visual Studio 2017
When I chose the first option: Visual Studio 2017 (presumably the existing instance), I ran into the cryptic "recursion too deep" error. I installed the SSRS extension for VS (as suggested by others on Stack Overflow) and tried running the SSDT installer again for the existing Visual Studio 2017 instance. I got the same "recursion" error.
I tried one more time, but this time chose the 'Install new SQL Server Data Tools for Visual Studio 2017' option. This time the install process completed!
Apparently there is an installer inconsistency between the latest versions of SSDT and Visual Studio. The suggested fix is to start with a previous installation of Visual Studio 2017, install the latest SSDT on top of that, and then upgrade Visual Studio. This is a very time consuming fix. It appears this is only necessary for the SSIS components - the SSAS and SSRS pieces are available as Extensions within VS, and I believe they still install successfully from there.
https://developercommunity.visualstudio.com/content/problem/258117/ssdt-failed-to-install-vs-2017-pro-1572.html
Please re-run the VS community 2017 installer or go to Control Panel-Programs and Features, uninstall the previous SSDT version for VS 2017, then re-install it, you can have a look at this similar issue.
If this issue persists, please use http://aka.ms/vscollect to gather the installation logs and find vslogs.zip under the %temp% folder, then upload the file to Onedrive and share the link here.
You should uninstall the current version of SSDT before install a new version.
If your computer have some pages blocked, you could download the specific version offline installer (Download the header, then use SSDT-Setup.exe /layout [Folder]) for the former version and new version of SSDT.
How I got past it:
Uninstall the Visual Studio extensions for Reporting Services (and Analysis Services) projects in case if you going to select them during SSDT set up. Note: remember to run VS as administrator to do the uninstall.
Reboot VS2017 (just out of general principle.)
i have already installed WDK. Any help?
enter image description here
Install Visual Studio 2015 or Visual Studio 2017.
Install Windows 10 SDK.
Install Windows Driver Kit (WDK) for your version of Visual Studio (there's a new version recently released for VS17).
Then you should be good to go. I've done this over and over repeatedly for a number of systems/new environments before, never ever encountered an issue when following this pattern.
I do not recommend having both Visual Studio 2015 and 2017 installed at the same time, or multiple SDK versions though. I've seen way too many conflicts due to this in the past.
I'm doing an unattended installation of Visual Studio 2015 Community Edition from a network share using the following guide: https://msdn.microsoft.com/en-us/library/ee225237.aspx
I've done everything as directed (and have successfully done this before with VS 2015 Enterprise) however for some reason the install isn't completing properly. It seems as the the Visual Studio executable is missing after the installation has finished (this happens doing it both in attended and unattended mode). Has anyone else run in to this issue before?
It seems I have found a devenv.exe in the Microsoft Visual Studio 14.0\Common7\IDE\ folder that launches the IDE. It seems that my unattended install didn't set up the icons for the IDE properly either in the start menu or on the desktop.
I have Windows 8 machine.
I had visual studio 2010 and Visual Studio 2012 installed on my computer.
I installed the visual studio 2013 preview, and the 8.1 WDK.
After I installed Visual Studio 2013, my old project in C++ wasn't able to be compiled (in Visual Studio 2012) so I uninstalled Visual Studio 2013 and the WDK.
But the issue remains, i cannot compile my C++ project. I get error message such as "Windows.h cannot be found" I looked at the include directory and saw that I have the following include: $(WindowsSDK_IncludePath). but when I open "Macros>>" I can't this macro "$(WindowsSDK_IncludePath)".
I tried to uninstall Visual Studio 2010 and 2012 and reinstall them but it didn't fix the issue.
Does anyone know what might cause this issue and how to resolve it?
In order to build windows 8 apps in visual studio 2013, you must be using windows 8.1. (defined here). This is possibly the issue.
You also wouldn't see the windows sdk include path because the wdk would be uninstalled. I would recommend one of two things
get visual studio 2012 again, and download the windows 8 sdk
get windows 8.1, then install visual studio 2013, and use the windows 8.1 sdk
I know, its quite silly.
I have a newly built Windows 8 VM with VS 2012 Premium running on it, when I try open any sln file I get the following modal pop up error
Visual Studio 2010 Shell
Invalid license data. Reinstall is required.
I can open the sln's if I open up VS and then do project open, this is really annoying, any ideas how I fix it?
*Note I have done a VS repair and it didn't solve it...and I never had any VS RC release on the machine, all new build with s/w downloaded from the MSDN
Cheers
I encountered the same exact error when I created a solution with a full version of Visual Studio 2012 Professional on one machine and then tried to open the solution file with a copy of Visual Studio 2012 Express on a different machine. I got the error when double-clicking the solution file, but not when loading the solution into an already opened instance.
I fixed the error by opening the solution file (.sln) with notepad and changing the line that says Visual Studio 2012 to say Visual Studio Express 2012 for Windows Desktop.
After that, I was able to double-click to open the solution file on the machine that has Express installed.
I'm using VS 2013. I fixed this by right clicking the .sln and setting the Open With parameter to visual studio 2013 and not VS version selector or VS 2010.
I have faced the same problem. When I set the system Date and Time to the current Date and Time, The Problem solved by itself.
It looks like the .sln extension is owned by "Visual Studio 2010 Shell" a minimal version of Visual Studio that ships with products like SQL Server and Office to provide support for add-in development without any other features. Since this is a minimal version, it's unable to load any project type that ships with Visual Studio Express, Professional or above.
The same may happen when you have Visual Studio Express installed next to a full version of Visual Studio.
This may happen when you install an older version of Office or SQL Server after having installed Visual Studio. The old installer will hijack the extension.
To repair this problem:
use the "Open With" option of Windows and select the "Visual Studio Version Selector" as your default action.
Or open the "Default Programs" option in Windows, look up the .sln extension and make sure it uses the "Visual Studio Version Selector" as default:
Or locate Visual Studio 2012 in the Programs and Features window of Windows and chose "Change", the Visual Studio installer will pop up, chose "Repair" to have it repair the file associations and any other problems that may arise by installing Visual Studio versions in reverse order (it may for example mess up the MsBuild directory as well).
Remember that when Visual Studio 2010 was released, it could not yet know what Visual Studio 2012 would change, as such, it's best to install versions of Visual Studio in the order they were released. This may sometimes prove difficult, as other products may install Visual Studio versions without you knowing.