I have VS2010 C# Express installed, and it was working just fine. However, as of today, none of the menus seem to open the Explorer menus.
For example, I was working with an XNA project when I first noticed it, I went to add an existing file to my project, and when I clicked the option in the context menu ... nothing. After poking around a bit, I noticed that I can't even click the open file button or Ctrl-O. I can confirm it's only VS that is affected, all my other programs work just fine.
Now, I have tried to repair the installation for it, and failing that, I did a complete uninstall, followed by a reinstall, but no luck. I also tried the Professional version and had the same results.
EDIT: Now, a few days later, it seems to be working just fine. I don't know what caused it, but I know my HDD might be slowly failing, but I wouldn't think the two are related.
It turns out the resolution was to run it in Compatibility Mode.
Related
I have a Blazor application using Visual Studio 2019 version 16.10.4. Every time I publish to an IIS server using the Publish... command from the Solution Explorer, Intellisense stops working in the .razor file that I have open and all text coloring goes away, so that all the text becomes the same color (and all auto-indentation stops working). If I close the .razor file and reopen it, Intellisense and colors start working again.
Is that a known issue, or is it a problem that I can fix? I've seen other posts about Intellisense not working in Blazor, but those all seem to be older posts with older minor version numbers of Visual Studio, and they don't mention the problem occurring only when publishing.
This kind of thing happens all the time. The solution is to jiggle it a little bit: close and re-open the file, restart VS, delete bin files, etc. etc.
In Blazor, there are a couple other common culprits. EventCallback with a declared Type often complains that it can't covert the type, even though if you ignore it, it will still compile and run.
It appears a fix is coming for this. As much as it's a frustrating issue, at least it will be resolved soon.
https://github.com/dotnet/razor-tooling/issues/5103
This is happening with all new .Net Core projects (Console App, Class Library, Web Application etc), no matter the directory or drive I put them in.
The project is created and loads, but only the absolute bare minimum skeleton-of-a-skeleton is shown.
Quick screenshot:
If I tell it to show hidden files, I can see the whole project has been made:
Now if I select any file or folder, right click and choose 'Include in Project', nothing happens! I've tried closing and reopening Visual Studio, and have tried restarting my laptop, but still nothing happens.
Other projects work fine, e.g. WPF, Xamarin or anything that isn't done via .Net Core.
Is there a setting I may have missed or need to change somewhere? It's a strange issue indeed.
Thanks.
Turned out reinstalling Visual Studio was the only answer.
As in, full uninstall, delete the leftover folders in the old install location, then reinstall from scratch.
If I tried the update option, it failed at the start of the download. My guess is something messed up in Vistual Studio. It was fine before. The only thing I changed was that I recently installed AVG Antivirus, which seems way too strict on what processes it allows and disallows. AVG is now uninstalled.
Im tearing my hair out with this one Im afraid and am down hours and hours.
Firstly I wanted to install VS Community to use with Unity. Im running windows 8.1 pro.
But I had trouble installing. Long story short there were some fonts in windows\fonts that the VS installer didnt like. So I moved the fonts and the installer ran through successfully. I then installed the VS 2013 Tools for Unity.
So then I imported the Unity VS tools to my project. Now my unity project hangs when unity opens. I fixed unity by removing the Unity VS stuff form the project directory.
I started getting errors on screen that said "An unhandled exception System.Configuration.ConfigurationErrorsException) occurred in ZAPrivacyService.exe[3168]
The Just In Time Debugger was launched without necessary security permissions etc etc
Also the above error message appears very frequently and even if i ignore the dialogue it just keeps popping up every minute or so. I just off the JIT prompts but then I get an error message saying that no JIT is available. instead of the other error message. ZAPrivacyService seems to be part of ZoneAlarm. So I downloaded and reinstalled it. No joy. I tried uninstalling the Unity VS tools. I then went to Programs and Features to remove VS. However when I click on VS I only get the option to change. So I click change and the VS splash screen briefly appears. Then nothing. I also tried rerunning the VS installer(from the ISO and the web exe) and the same thing happens.
I do want to get VS running I thought a reinstall could fix it. But not to even be able to reinstall.....
Also how can I set Vs to ignore everything except the projects im working on IN VS?
Any ideas????
Thanks
Recently, the editor for VS2010 suddenly became slow when I installed some extensions then uninstalled them. The program itself is running fine and starts up in seconds. Jumping around the menus is lightning fast, but editing code, there is a 1 second lag between the keyboard and the editor.
This happens on a brand new console application project with nothing in it. I have also uninstalled all extensions, resharper etc. The only extensions remaining are VisualHg, Ankh and Nuget.
I have an i7 with 16 gigs of RAM so hardware is NOT the issue.
Is there some sort of cache or files that VS could have locked onto?
How can I figure out what is causing the issue?
Well thanks to #jv42's suggestion, I installed the perfwatson extension and that sorted out the issue. I've since put some of the extensions back and VS2010 is running better than ever before.
I still don't know what caused the issue.
I would find a rollback point before you installed the plug ins. You could have malware that installed with the plugin but was not part of the uninstall. It could just be that the uninstall did not remove something it installed that was causing the problem. It is most likely going to be far faster for you to find a rollback point and start there than to try and figure out what process is causing you the problem and where it is hooked into the registry.
Try resetting your settings from the command line back to the factory default. Warning You will lose all your settings!
devenv /resetsettings
You can back them up, as well as reset, using this article.
finally refer this to fix my problem.
solution is:
Debug->Options and Settings->Debugging -> Symbols
change from All modules,unless excluded to Only specified modules
details:
here
I have a Visual Studio 2010 solution containing several C# projects, with Resharper 5.1 installed and enabled. All these projects target the .NET Framework 4.
This solution has been working fine for months, but this morning I got the following message when the solution was loaded:
I've looked around for an explanation on the meaning of this message, but with little luck.
Additionally, I haven't been able to repro this error, and it doesn't seem to have broken anything on my project.
Still, I don't like these kind of unexplained errors, so I was wondering if anyone reading this knows the root cause?
Hmm, that's special. It must be a debugger notification, the part of VS that 'attaches' and makes "Managed" a category. The other category is "Unmanaged", a different kind of debugger interface. It clearly lost its marbles there.
Counter-measures, in order, are:
Restart VS.
Reboot
Install Service Pack 1, it has many debugger fixes.
Consider moving 3 up the list if you haven't installed it yet, there are a ton of bug fixes and tweaks and works well.
In Visual Studio 2012 and Windows 8.1, I had this problem,I changed X86 from Solution Properties/Build/Platform target then my problem resolved.
This has been nagging me for a while. Finally I found a solution.
When I press the help button they suggest I sort out the attached debug option. Without any result I finally managed to check the Enable SQL Server Debugging option under Project Properties - Debug.
I have the exact same setting as you: VS2010 with several C# projects pointing to Net 4 and Resharper 5.1. I'm on Windows XP SP3
I was getting the exact same error, along with an empty VS icon in the taskbar.
The empty icon got away when I shifted VS to my main monitor (I have 2) and restarted. It seems that VS doesn't like to be in the second monitor.
As for your error, I cleaned up the Resharper cache (I'm storing it in the TEMP folder, not the solution folder) restarted, and didn't get the error again
In Debug Menu - GoTo Solution Properties and select debug tab and tick the ENABLE SQL SERVER DEBUGGING checkbox