I downloaded the AWS Tookkit for .NET a couple weeks ago and it was working fine.
http://aws.amazon.com/visualstudio/
For the last couple of days, I have not been able to open it in either Visual Studio 2010 or Visual Studio 2012.
I have already uninstalled it, rebooted, and re-installed (multiple times)
I can choose it from the View menu, but when I select it, nothing happens.
I'm just looking for some direction to see what I can do to resolve this.
I figured it out. I had to uninstall the Toolkit, then go to the profile on the PC and delete the whole AWSToolkit folder, finally I re-installed it. It allowed me to bring it back up and and browse everything.
Specifically, you want to delete the folder found at: %USERPROFILE%\AppData\Local\AWSToolkit
Related
First of all, I am trying to open a support request with Microsoft about this issue, but their support reporting portal isn't working. I have resorted to Stackoverflow because I have no way of getting to Microsoft.
Yesterday, I started updating Visual Studio 2022 from Visual Studio Installer by mistake and paused it shortly after. Today, I tried to open a project but Visual Studio seemed unavailable. At that point I remembered about the paused update and re-opened the Visual Studio installer. I tried to Resume, and I got the below error. The Modify and Remove options give out the same error too. There is no Repair option.
Sorry something went wrong
The dependent package of
'Microsoft.VisualStudio.Debugger.Concord,version=17.1.33203.90,productarch=x64'
cannot be found: Microsoft.VisualStudio.DebuggerClient.Concord,
version=[17.0,18.0].
I also tried Restarting and deleting temporary files using the Disk Cleanup tool - no difference.
I have tried to force an uninstall from the Add or Remove programs but this still redirects me to the Visual Studio installer.
I have tried to research this error online but found nothing.
I did not fix the issue but at least I managed to uninstall the Visual Studio instance to be able to start from scratch again. If you do not want to go down the route of uninstalling, feel free to try the steps as suggested by #garbagecollector.
I deleted the installation folder for 2022 from ProgramFiles.
I deleted the Visual Studio installer from Add or Remove programs. (Note: This actually uninstalled a working version of Visual Studio 2019 that I had, and left the messed up version of 2022 with the same issues, so beware if you do not want to uninstall another working version of Visual Studio)
Then I ran InstallCleanup.exe via CMD (in admin mode). Refer to the "Remove All with InstallCleanup.exe" section within this article. This seems to have cleared all Visual Studio related files including the Visual Studio
installer, and I could re-download the installer for Visual Studio
2022 Community edition and start afresh.
I faced the same issue today and could solve it by removing corresponding dependencies from _package.json files from C:\ProgramData\Microsoft\VisualStudio\Packages\[PACKAGE_NAME] folders.
I am not sure whether you can repair your installation this way, I tried only with uninstall.
So in your case edit this file:
C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.Debugger.Concord,version=17.1.33203.90,productarch=x64 and remove the line marked with "-->" under "dependencies":
{
"id": "Microsoft.VisualStudio.Debugger.Concord",
...
"dependencies": {
...
--> "Microsoft.VisualStudio.DebuggerClient.Concord": "[17.0,18.0]"
}
}
In my case I had to repeat this procedure for three or four _package.json files.
I am currently working on a new unity project and to be honest i am new at this.
I need to use the InputSystem package but Visual studio does not recognize it.
This is the version of my VS. Microsoft Visual Studio Community 2019 Version 16.9.3 and the version of Unity is 2020.2.1
As you can see by the picture, my VS already knows that I am working in a Unity project.
So the first thing that I tried doing is to regenerate project files but it didnt work. I also selected my VS as my default external script editor.
This is my external tools.
I re-installed VS using unity hub but nothing happend.
Do you have any suggestions? I followed some tutorials I saw over the internet but I am still getting no positive results and to be honest, I am getting out of ideas.
Just tested out the package installation. I installed the package in a fresh, empty Unity project. Here are the steps that I went through which worked in my case:
Locate the Input System package in the Package Manager
Click install
A warning prompt will appear, click yes
Unity Editor should now get re-launched on it's own, wait for that to happen
If Visual Studio is open, close it
Open Visual studio - right click on the Assets folder and select Open C# project
UnityEngine.InputSystem namespace should now be available, if not, re-open Visual Studio one more time
Let me know if it works for you.
For me works when I install .NET and .NET Core and reboot the computer. (made this on Windows)
https://dotnet.microsoft.com/en-us/download
https://dotnet.microsoft.com/en-us/download/dotnet/3.1
When I start VisualStudio it frezzes on the start screen. But when I start it a second time while the first instance is open the second instance works fine.
It's not that important but what could cause that problem?
Not sure. Sometimes some Visual Studio extensions are locking up Visual Studio.
I think by default Visual Studio tries to update these extensions
that have been installed automatically.
Recently I was trying to run Visual Studio (at Home) and it would freeze if I tried to open a specific project. But I was busy, so I didn't pursue it further and did other things. Then a week or a few days later I tried to run Visual Studio (at home), and it locked up when I ran it. I tried really hard to fix it.
There is a way I don't like where you can delete all or most of the
extensions from the place Visual Studio installs them, but this is
messy, and it is easy to get rid of something you need, and may hard
to get it back where it works correctly again. So I now recommend against this since there is a better solution now, below!
I searched to find a solution, and someone on a Microsoft board I think said to run from a command prompt as Administrator: DEVENV /RESETSETTINGS, I tried that and it didn't work for me. Then I thought, run DEVENV /? to see what I can see, and I saw :
DEVENV /SAFEMODE
So I tried that and it worked! Note: it was still being run from the Visual Studio Developer Prompt as an Administrator.
Visual Studio loaded up correctly, and I was able to look at the
installed extensions.
Eventually I noticed that they all or a lot of them were disabled (probably because of this SAFEMODE parameter), and I noticed that it the most recently updated were at the top of the list. I noticed that a lot of them had been automatically updated by Visual Studio and started Uninstalling a bunch of the more recent ones, and reverted at least one of them, then later uninstalled it. Eventually, after about 6 to 10 uninstalls, I got it to where Visual Studio would load normally, without the /SAFEMODE parameter! Cool!
So I turned off the automatic updates, so this will never happen automatically again. If I load a new extension or update and existing one manually, I should always exit Visual Studio and reload it after not doing too many updates or installing too many extensions to see if these extensions allow Visual Studio to load.
Sometimes an extension will not freeze Visual Studio, but will have errors. The ones that are the big problem are the ones which prevent Visual Studio from loading all the way and freezing it up. But with the above solution, you can eventually, cleanly, uninstall all the latest updates or new installed extensions until you finally get Visual Studio to load normally!
This workaround should be more widely known, so I am putting my solution to it here. Hopefully what I found should help someone else who is in a hurry, without having a lot of time to burn trying to get Visual Studio running again without freezing!
I use Visual Studio Community 2017, and I got this same issue on startup until I stumbled on this solution that deals with some corruption in the .suo file. Before I open Visual Studio for the day, I first delete the .suo file in my project folder, and it starts up just fine.
It's in a folder called .vs next to the .sln file. You may have to go to folder options View and check "Hidden Items" in order to find this folder. Dig down in that folder and you'll find the .suo file. Delete it. When you startup the project in Visual Studio, it will automatically create a new .suo file. So you'll have to do this every time you reopen.
I have recently installed Microsoft Visual Studio 2015 Community Edition on my laptop.
Since the time of installation I have been facing a few issues.
I was not able to even access the New Project option itself.
Some of the times I will be able to access it however, sometimes it does not even allow me to access a single file of my solution in the startup itself it gives me an error.
I have attached a set of five screenshots in this query. There is some blank space after users path, I removed an extra folder name(username) from the path so dont get confused with that.
The detail of all the screenshots are as follows:
1) This is the image I get when I launch the Visual Studio on my laptop.
2) Once I click 'NO' option on the first dialog box I get a new one stating an error with the source code.
3) Once that is done, I move onto Solution Explorer to access the solution and I get this log.
4) When I try to access the tools tab to check for options I get this error message.
5) I had even tried to create a new project and the following error provided in this screenshot would appear.
I am not able to understand where I could have gone wrong or what happened that has corrupted the application to this extent. Is it an installation issue or are there some bugs in this version of Visual Studio, if there are any I would be more than happy to move to previous versions as I was a lot happier with them than this one.
If someone would help on this concern I would be really thankful.
Regards,
Harrisson
First, I went ahead and uninstalled the current version of Microsoft Visual Studio 2015 from my system. Then, I searched and removed the data from the temporary files related to MS VS 2015 from the following paths:
C:\Users\Username\AppData\Local\Microsoft\VisualStudio
C:\Users\Username\AppData\Roaming\Microsoft\VisualStudio
Once this had been done, I went ahead and installed Visual Studio 2015. After installation, I installed the additional support directories for Visual C++. You can do the same for the platform you wish to work on.
Then I installed updates from the following link:
https://www.visualstudio.com/en-us/news/releasenotes/vs2015-update3-vs
Once I started the solution it worked perfectly fine after that with no errors.
I can successfully reproduce the problem at will. Below is my steps:
Environment: windows 10 Professional 64bit
Run vs_community_ENU.exe to install
Choose the Microsoft web and Developer Tools
Let it done installing
Open it for the first time, I can see the ASP.NET Web Application
Close the Visual Studio
Open it up for the second time, it will show some upgrade: "Scanning new and updated MEF components..." and two or three more of
the undated
New project no long shows asp.net web application along with other templates
How can I fix this problem? I uninstalled and reinstalled it for 5 times already and the same thing happen again. I even installed VS2015.1.exe but nothing happened
Delete the contents of the following folder:
%localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache
I had to delete the contents of %localappdata%\Microsoft\VisualStudio\14.0\MEFCacheBackup
as well as
%localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache
The deletion of both these folders sorted my issue :)
I found an answer. If I run "Blend for visual studio" shortcut then in the new project, there is no asp.net templates along with others. But if I choose the standard "Visual Studio 2015" then those templates are there... So glad to find the answer because I keep remove and reinstall each time I accidentally close visual studio 2015 community