I recently installed VS Community 2019, version 16.6.3 and when launching right after the splash screen is shown, I get the following error message:
I have reinstalled it twice and ran the repair service, and still get this error. Has anyone else experienced this and been able to fix it?
Related
Afternoon all,
I had been using the Visual Studio 2022 Preview. Recently I decided to switch to the Release version. I uninstalled VS2022 Preview and installed the 2022 Community Release.
The install runs fine and completes with no issues. However when trying to run VS2022 It comes up with the error attached below.
From my talks with MS found at https://developercommunity.visualstudio.com/t/Unable-to-launch-VS-Comunity-2022-after/1596301?entry=myfeedback&viewtype=all It appears VS2022 Community should be running version 17.0 of the .Threading DLL. However no matter what I have tried it refuses to load.
I have run the uninstaller with -F. Re-installed several times.
Attempted to install 17.0 to the GAC but this does not change the outcome
As per the post on the developer community pretty much everything short of re-installing windows (Which I am 100% trying to avoid)
I ran the FusionLog viewer (Attached) and it looks like there is something re-binding this to the 17.1 .threading version however I know very little about how this works and where I might find a solution, Hence, I am here :). Although my post on the DeveloperCommunity is still active I'm hoping a resolution here maybe faster!
Thank you!
I have this error too, and its becouse you dont have defined startup project.
Right click on your startup project and choose "set as startup project".
Actually the above is incorrect, you can't even get to the startup screen.
The correct answer is you need to remove the V15 version of the dll from the GAC. Instructions from MS can be found here.
Yesterday I updated SSMS from 16.3 to 16.4.1, rebooted and then installed the Window 10 Anniversary Update from Windows update. Everything on my PC seemed to be running fine.
However, trying to open SSMS today for the first time since the update and nothing happens. There is no error message and nothing is created in Event Viewer.
I have tried repairing the installation, which didn't fix the problem, and reinstalling the application which again did not fix the problem.
I can see in Process Monitor that the process exits with status 0 and it doesn't appear there is any effort made to write to a log file.
Has anyone encountered a similar issue with this release?
Edit: The problem is resolved by uninstalling 16.4.1 and reinstalling 16.3, which makes me think something is broken in the latest release.
It appears the solution, after rolling back to 16.3, was to install the Community edition of Visual Studio 2015 and then install 16.4.1 again.
I attempted to repair my existing install of Visual Studio 2013 today (I installed it last night and got an unknown error, followed by a ton of package errors on launch) and was greeted with this message:
Googling didn't reveal anything, so I thought I would ask here. Here are the logfiles I got with the log collector as discussed here.
Can anyone tell me what's going on?
This is also the result of running Update 4 (Nov 2014) after applying a more recent update to NuGet Packager, such as this one from April 2015, or via the Extensions and Updates GUI in VS2013.
If you check in About Visual Studio, you should see the NuGet Package Manager with a version number that is more recent than the one you would get with a fresh install, even if you ran Update 4 after the install.
I managed to solve this problem by installing NuGet 3.0 after downloading it here and opening the CMD prompt as administrator.
Recently, I needed to refresh my Windows 8.1 PC, and now that I have finally finished getting all of my programs reinstalled and everything is back to normal, I am ready to finish work on my Windows 8.1 app, but I am having an issue with compiling my apps. Every time I try to compile, I get the following error.
Now normally when I need to refresh my developer licesnse, Visual Studio tells me, but this time I didn't get any prompt at all, and that is the error that I got when trying to compile. How can I fix this? I am installing updates for Visual STudio at the moment, and I am hoping that doing so will somehow magically fix the problem, but I am also aware that it probably won't.
EDIT: Now that I have updated, the message has been shortened to "Can't resolve Windows.metadata."
For some reason, even though the Windows 8.1 SDK is supposed to be installed with Visual Studio Ultimate 2013, it wasn't for me. I was able to find the Windows 8.1 SDK by Googling it, and it came up as the top result. I installed it, and suddenly all of my errors went away and Visual Studio started recognizing them as legitimate Windows 8.1 app code.
I've been trying to install Visual Studio 2013 for HOURS and I have no idea what to do. Every time I launch the setup I get:
"Setup detected an issue during the operation. Please click below to check for a solution and help us to improve the setup experience".
After that it tells me to check my CBS.log file, and I understand none of the contents, but here it is: http://pastebin.com/zQdfHW7n
I am running Win8.1 preview.
I've tried the following:
- Running it as admin
- Running it in comp. mode (WinXP, Vista, Win7, Win8)
- Uninstalling VS2012 (but getting the exact same error)
Someone please help! :(