Related
After updating to visual studio 2013, update 4, the TEST option is missing from my screen, I thought Visual Studio update 5 would fix it, but it did not. "TEST" is missing from my options and I don't know why.
I have tried resetting the settings, it does not help, reset settings:
I cannot add test via TOOLS -> CUSTOMIZE -> COMMANDS -> ADD COMMAND, it is not there.
What edition of Visual Studio are you working with? Have you ever had
the TEST menu present?
Yes, I've run tests before, I'm currently
at Visual Studio 2013.5 - Premium flavor
#OP answered:
I don't know why, but uninstalling Office Tools extension seems to have fixed it.
I wanted to provide an explanation for why Menu's can go missing. One reason for this is when you install another component for Visual Studio, like Team Foundation Client or in this case Office Tools extension. They "may" automatically select a different setting. To check if this is the problem:
In Visual Studio click Tools Menu > Import and Export Settings:
See here how Project Management Settings is selected, that is the wrong setting if you're a Developer.
To see the missing developer menu's reset it back to a developer setting.
Ref: http://blog.accentient.com/a-visual-studio-mystery-the-case-of-the-missing-menu-items/
I had the same issue in VS 2015 Update 2 Community and the culprit apparently was AppInsights extension (https://github.com/dotnet/roslyn/issues/11653). To provide some detail:
Noticed test menu missing in existing solution where I previously ran tests
Made a blank test project, still no test menu
closed vs and reopened. Still not test menu
Got error referencing C:\Users{username}\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml
Last error in there was NullReferenceException in CodeLensIndicatorService
Googling that found link above, tieing to this add-in.
disabling it fixed the issue and test menu not appears and I can run tests.
Forgive me if I complain a bit, but if any VS team is reading: Under no circumstances should an add-in failing cause a built-in menu to not appear. As much as this is a bug caused by the the various add-ins, it is also a flaw in VS IMO- and one that is not trivial for end-users to connect the dots on.
Somehow the settings (settings have menu items configuration also) for your visual studio may have issue. Either you can try reset. Only in case that doesn't work you can always customize your menu item. so
Tool -> Customize (by default standard should be selected)
select commands tab and then menu bar option. You can see options to add commands. Under that you can select test so make testing option visible.
Also for testing test case, you can always right click on class and run it.
Hi Please try to reset all setting
http://blog.accentient.com/a-visual-studio-mystery-the-case-of-the-missing-menu-items/
If not then there is workaround to add your setting
http://blogs.msdn.com/b/visualstudioalm/archive/2012/09/11/visual-studio-2012-where-is-the-test-toolbar-couldn-t-find-it-anywhere.aspx
After doing close visual studio instances and reopen it.
I don't know why, but uninstalling Office Tools extension seems to have fixed it.
Edit: I tried to reproduce this bug, I ran the VS2013.5 update and clicked repair. The update took +5 hours, figured it got stuck. So I cancelled it, got stuck cancelling. So I ended the process. Now I started visual studio and TEST is missing, basically my visual studio installation is messed up I think.
Edit: Found the culprit, it was Microsoft Intune Endpoint Protection that was installed on my pc. It basically scanned everything and when visual studio got updated and files were written to the disk, something went wrong and corrupted my install. I turned it off by excluding C:\* from being scanned and ran VS2013.5 update and clicked repair. Everything is fine now.
I'd like to add a custom control to my VS toolbox but the VS crash when I click on toolbox -> mouse right-click -> 'choose items...'. I read it's a know VS bug (since VS 08, from what I've read) that wasn't fixed yet.
Here's what I've tried so far:
start in safe mode: WDExpress /safemode
run as adm
Reset the Toolbox.
Check for the .tbd files and then delete them. But actually there are no any .tbd files in those folders:
C:\Users\myUsername\AppData\Local\Microsoft\VisualStudio\10.0
C:\Users\myUsername\AppData\Local\Microsoft\VisualStudio\12.0
(I guess there are two folder because I have the VS WEB installed apart from the VS 13, which I'm using and haveing that issue)
All those answers.
Try to clear this registers, which didn't exits in my installation.
NOTE: I didn't have any thrid party libraries installed. This is the very first one I will install.
But it didn't made any difference on my case and still crash. Any workaround? maybe add it via command-line or something? I'm pretty sure reinstall it will not make difference either.
EDIT: I didn't find the devenv.exe (to run /safemode flag) in my VS installation folder but I read WDExpress is the equivalent to so I ran it.
EDIT 2: This is the screenshot before the crash:
EDIT 3: Here's some information from the Event Viewer of my system.
Not sure if it helps. My giess is: it did crashed when trying to get the version of the microsoft.teamfoundation.discussion.client.dll dll.
After hours I finally I fixed it :) I hope it useful to anyone. This was pretty simple: control panel -> Add or Remove Programs -> select the Visual Studio -> Add or Remove -> will open the VS uninstall program, click on Repair button. After repair finishied I restarted the machine and worked fine for me.
My Tools:
Visual Studio 2012 Ultimate + Update 1
ReSharper v7.1.25.234
My Solution Build Status: Build Successfully
But when I install ReSharper and ReSharper code analysis is enable, many keywords of my code are red with this error:
"Cannot resolve symbol XXX"
Another picture of my project >>
The ReSharper “CANNOT RESOLVE SYMBOL” errors are everywhere, but my project build process is successfully, and it works correctly.
Additional Note: If I disable ReSharper Code Analysis, my project will be Normal, but I want to use ReSharper code analysis.
I tried ReSharper → Options → General → Clear Cache. But I still have this problem!
One month ago, I got these errors when I uninstalled Visual Studio 2012 RC and installed VS 2012 RTM.
I've already uninstalled and installed ReSharper again. But I have this problem yet!
My solution has five projects >> two loaded projects (main project + resource project) and three unloaded projects
I realize that my Visual Studio also has bigger problems (More information on Stack Overflow)
I can't add any reference to my projects (even inside new solutions and new projects)
I can't install any package (by "Packet Manager Console" or Manage NuGet Package)
I can't update any package (by "Packet Manager Console" or Manage NuGet Package)
I've done a lot of suggestions (of myself and others)
Re-resister some DLL files
Using some windows and registry repair tools
Remove ReSharper
Repair Visual Studio
and...
But I could not solve it.
I'm thinking of installing a new Windows :(
What is wrong, and how can I fix it?
Try Visual Studio → menu Tools → Options → ReSharper, Suspend button and Resume again (no need to close the window). This works in my case.
VS -> Tools -> Options -> ReSharper Suspend button
Clear Contents of -> AppData\Local\JetBrains\ReSharper\v7.1\SolutionCaches
VS -> Tools -> Options -> ReSharper Resume button
This worked for me (VS2012u4, R# 7.1.3):
Resharper > Options > Environment: General > Clear Caches
Restart Visual Studio
Clear Resharper cache: Resharper -> Options -> General -> Clear Caches, close and reopen the solution. It worked in R# 9.0 Update 1
This happens in ReSharper when you have two different versions of the same library in your solution. For example project A references automapper version 1.1 and project B references automapper version 1.0.
Visual Studio will often compile and run as expected in the situation as it chooses one of the DLLs to bind to. However ReSharper gets massively confused. For me this should be a ReSharper error that it asks you to resolve rather than just going bonkers.
UPDATE:
I ran into this two days ago (a day after I made this post) by total coincidence and came across this link where they say that it is caused by a bug in the VS API. I tried everything that they recommended and was unable to resolve it even temporarily: I had Autofac 2.6.x that I'd downloaded from google.code and then swapped it over for the NuGet package version and it willfully refused to see the new reference no matter what I did.
They suggest installing the R# 8 EAP but for me it was less hassle to just downgrade to the old version of Autofac.
Not much in the way of help, but maybe useful.
This was happening to me with Visual Studio 2015 and ReSharper Ultimate 10.0.2. I tried pretty much all the solutions written prior to this answer (apart from any reinstallations) and nothing worked.
I got it working again with a variety of the above steps in a very specific order:
ReSharper → Options → Environment → General → Clear Caches
this must be done before suspending ReSharper as otherwise this option is unavailable
this clears out the files in C:\Users\YourUsername\AppData\Local\JetBrains\Transient\ReSharperPlatformVs14\v04 as mentioned in some other posts
Tools → Options → ReSharper Ultimate → Suspend
Close Visual Studio
this actually performs the ReSharper cache clear
Open Visual Studio
Open the solution
I waited for Visual Studio to detect there were no code issues in IntelliSense and may have performed a build at this point.
Tools → Options → ReSharper Ultimate → Resume
Hopefully after the last step you can breathe a sigh of relief that you don't have to reinstall anything, I certainly did!
It's usually happen by config file corrupt or wrong detect.
Just delete .vs folder, restart VS to reset config. It will work almost case
I had similar problems and cleared the caches found at:
AppData\Local\JetBrains\ReSharper\v7.1\SolutionCaches
Solved the problems for me
Running VS2012 u3
I had the same problem (VS 2017). In my case it was different versions of target framework - one assembly targeted 4.52, another 4.62 - after setting those to the same version in both assemblies it started working again.
As you see, the solution is what everyone has already mentioned - simply by Suspending ReSharper, then Clearing the Caches, and finally Resuming it. But, no one mentioned how to do it without closing/restarting Visual Studio.
Just follow these steps:
Getting ReSharper Cache Location
Manually by going to ReSharper Options > Environment > General > Store Solution Caches in (Combo Box) (marked 2 in the image). Selecting Custom Folder, then Copying the location of the Caches Folder from the text box shown (marked 3 in the image). Reverting the settings back. The 1 marked shows the ClearCache Button. It's usually wouldn't work so leave it.
Suspending ReSharper
You can do this by going to Tools > Options > ReSharper Or ReSharper Ultimate > Suspend Now (Button)
Clearing the Cache
Go to the location copied earlier in step 1 and delete everything in that folder. And yes, I do mean everything.
Resuming ReSharper
You can do this by again going to Tools > Options > ReSharper Or ReSharper Ultimate > Resume (Button)
Above links of clearing the cache and/or suspending the ReSharper did not work for me. I just 'refreshed' the project, which was showing this problem, from the solution explorer and the problem goes away. Sadly, it keeps on recurring and only option it to keep on refreshing every time this problem recurs.
I have VS2012 with ReSharper 8.1 on Windows 8
I was just having the same issue with ReSharper 8.2 in Visual Studio 2013, and none of the usual solutions here of clearing caches, suspending ReSharper or re-installing ReSharper was working.
In my case I ended up solving it as follows... I looked at one of the symbols that it couldn't resolve and noted it was in System.Web.Http.dll. I then found that this was in the Microsoft.AspNet.WebApi.Core NuGet package. I used the package manager console to try and uninstall that package, except of course it told me that it couldn't due to other dependencies.
So I uninstalled each dependency up to and including Microsoft.AspNet.WebApi.Core, and then re-installed each package again in the reverse order. ReSharper picked everything up correctly as it was installed, and now seems fine.
I had the same issue and unloading and reloading problematic project helped me to clear out this issue for ReSharper. Hope this helps.
I ended up needing to request Resharper to clear its cache along with doing it manually through Windows File Explorer. This finally resolved the issue for me.
(As reported in many of the solutions here) RESHARPER > Options... > Environment > General > Clear Caches.
Close Visual Studio.
Go to this path in File Explorer for Resharper 10 in Visual Studio 2015: %localappdata%\JetBrains\Transient\ReSharperPlatformVs14
Delete all subfolders and their contents within that folder.
Restart Visual Studio, reload your Solution and wait for Resharper to initialize itself for the Solution.
For me for VS2015, I had to update Resharper to version 2016.2.2 to resolve the issue.
I had already tried (of which none worked for me):
suspending / resuming
suspending / clearing cach (using tools > options button) / resuming
suspending / clearing cach (using Windows file system) / resuming
moving cache to solution folder / restarting visual studio
many other combinations of all or some of above
I hope that may help someone.
Resharper -> Options
Caches -> Store solution caches in: (Change folder to another one).
Or try to manually clean up R# cache folder
I'm using 7.1, and this worked for me:
Uninstall resharper
go to %appdata% and remove JetBrains\Resharper and ..\Local\JetBrains\Resharper folders
re-install resharper
None of the cache cleanup worked for me. All of the symbols in any of our private NuGet repros just stopped being picked up with R# enabled, very frustrating.
I got this feedback from JetBrains support, which DID work, after toggling and restarting VS2019:
disable the following option - ReSharper | Options | Environment | General | Read solution model directly
I did everything above with no fix.
Then I did a step from another SO Q/A (don't remember which one) which was to set System.Web.Mvc to Copy Local true. Recompile my project and the errors went away.
When I set this assembly back to Copy Local false, the errors didn't return.
I my case, I tried all the suggestions above.
But, at some point I realized that the problem persists even if Resharper is suspended.
So, I looked for similar problem in VS itself and found the solution in the comments for the accepted answer in this SO post.
I'm listing my steps for brevity.
VS -> Tools -> Options -> ReSharper Suspend button
Build solution. Notice all references still unresolved
Clean the solution
Restart VS
Build the solution without Resharper. Notice all references resolved
VS -> Tools -> Options -> ReSharper Resume button
I am using VS2015, R#10. None of the suggested solution worked for me. I deleted the contents of the bin folder of my solution and rebuild the entire solution, that seems to have resolved the issue. Before deleting the contents of the bin folder, I had tried suspending and resuming R#, doing clear cache from R# -> option -> general setting, and also manually deleting the contents from \AppData\Local\JetBrains\Transient\ReSharperPlatformVs12\v01\SolutionCaches.. Hope it helps someone.
I was having the same issue in my Visual Studio 2015 with Resharper Ultimate and tried the solutions as suggested above, but none worked for me.
Then upgrading Resharper to latest release solved my issue.
What helped in my case after several of the suggestions above didn't:
Removed one project reference (of one of the libraries where ReSharper claimed not to be able to find it even though it was correctly referenced).
Use ReSharper’s "Resolve" on one of its usages to add the reference again.
After that, it worked fine, even though none of the project files were actually modified in the process.
I have the same problem.Clean Resharper cache and Suspend Resharper not worked for me.I just close visual studio, uninstall Resharper,and then install Resharper,the problem was gone.
I was referencing a NetStandard2.0 project that didn't get recognized by R#.
I cleared the caches but that did not help me.
Downloading the latest version and updating R# did work for me.
This is the version I'm now running:
JetBrains ReSharper Ultimate 2017.3.2 Build 111.0.20180201.63358
ReSharper 2017.3.20180201.111630
Just download R# and it will recognize already installed versions. Updating to the latest version is really easy.
When I disabled ReSharper, Visual Studio was also giving the same error, even though the project built successfully. What I did to resolve the issue was:
Remove the project from the solution.
Right-click the solution, Add Existing Project, select the project file and add it again.
After performing these steps, the syntax errors went away in Visual Studio, and after I enabled ReSharper again, it also had no errors.
I also had this problem. All previous solutions did not help for me or helped for a very short time.
In my case, the problem was that I connected the .Net Framework 4.7.2 project to a project that has version 4.5.2. After I updated both projects to version 4.7.2, the problem was resolved.
I think that to solve the problem you need to have the same version of the projects. Or connect a smaller version to a larger one, but not vice versa, as was the case in my case.
In Rider 2020.3 I just did a Build -> Clean, and then it worked.
For me, I think my solution just got caught in a weird state when I was changing which branch of my local Git repo I was on. Simply switching to the previous branch I was on before the problem started, telling VS to reload all the files, then switching back to the desired branch and reloading again fixed it.
We saw this problem as well, specific to files which were shared by multiple projects. There is a combo box in the upper left corner of the editor window that lets you switch project context for the file (and hence the references that impact symbol resolution).
Resharper makes it easy to accidentally open the wrong "version" of a shared file by its "go to file or symbol" commands.
Switching context back to the project I use in the solution was all I needed to do to fix this issue.
Somehow part of my syntax highlighting for C# code has disappeared in the VS 2012 IDE. Uninstalling, rebooting, and reinstalling does nothing, nor does resetting the colors in the options dialog.
Here are some examples of items which all appear in default (black) that normally have color which don't:
Attributes
System classes
My own classes
And here are some keywords that still have color:
using
public
void
var
for
Has anyone else experienced this and managed to fix it?
Here is a simple solution. Go to the directory where devenv is (for 2012 RC), and type devenv.exe /setup. It will fix your problem.
devenv.exe is usually in something like C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE.
Edit: It has been suggested that you do this from the Visual Studio command prompt (Start>Microsoft Visual Studio>Tools>Visual Studio Command Prompt), and/or make sure your command prompt has administrator permissions.
Note for others: This has a very good chance of working for many other versions of Visual Studio, including 2008, 2010, 11 beta, ...
My problem was limited to having the "DateTime" type not showing up in light blue like other class names. I fixed it by simply switching back-and-forth between VS Themes. Discovered by accident. Much quicker than reset settings or repair install...
VS menu Tools -> Change Color Theme
This is what worked for me:
1 - delete all in C:\Users\userNAme\AppData\Roaming\Microsoft\VisualStudio\11.0
2 - open vs console as administrator, and run:
devenv.exe /setup
devenv.exe /ResetSettings
This will reset all your environment settings.
If none of the above work for you, delete all GUID-named folders under this registry key (make sure your Visual Studio instance is closed):
If you're using Visual Studio 2012:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\FontAndColors
If you're using Visual Studio 2013:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\FontAndColors
If you're using Visual Studio 2015:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\FontAndColors
Restart Visual Studio, and you should see a few various "User Types" to configure. You can then import your Fonts and Colors that you backed-up, and everything will be good to go. This may also work for previous and future versions of VS, but I have not tested.
Disclaimer: Make sure you export/backup your current Fonts and Colors settings before making these registry adjustments. I cannot be held responsible for you losing your configs :)
If you still have this issue try ResetSettings (worked for me)
NOTE: this will reset the Visual Studio 2012 settings :)
1) close vs.
2)open cmd (as administrator).
3) go to devnev.exe folder (something like "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE" ).
4) type "devnev.exe /ResetSettings"
5) open vs and look at the beautiful colors
Found the source of the problem:
If you have the "Productivity Power Tools 2012" installed,
you should go to Tools -> Options -> Productivity Power Tools
and turn off the "Colorized Parameter Help" option.
This fixed the syntax highlight problem.
If anybody runs in to the same problem for Visual Studio 2013 as I did, the only solution that worked for me was to first close VS2013 and then delete the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\FontAndColors
After reopening VS2013, my syntax highlighting for types was restored.
Prior to deleting the registry key, I noticed that all of the "User Types..." settings in the Fonts and Colors section of Tools > Options were missing. Deleting the registry key restored them. They attained their default values which gave me the syntax highlighting colors I was looking for.
This was the only solution that worked for me. Switching themes, resetting my personalized settings to defaults, running devenv.exe with various command line switches to setup/reset Visual Studio did not work.
I also created the following bug report with Microsoft on their Connect site:
http://connect.microsoft.com/VisualStudio/feedback/details/810985/incorrect-syntax-highlighting-for-c-types.
For me "Productivity Power Tools 2012" was the cause. Nothing suggested here helped. After removing the Power Tools the colors came back.
I did all the things listed here and still nothing (VS2013 Update 3). I tried /setup, /resetsettings, deleting the stuff in AppData, deleting the registry keys. Still, User Types wouldn't be highlighted even in the default color scheme.
What helped in the end was opening the Fonts and Colors dialog, selecting Identifier, and making it Bold. Then removing the Bold. Instant fixage!
I had the same issue....just uninstalling and re-installing alone did not correct the problem. After I un-installed, deleted all remnants of VS 2012 in program files, removed all related registry keys, and deleted the VS 2012 folder from My Documents, then re-installed, user types showed up in the display items in fonts and colors and everything went back to normal. My guess is that it was an issue with one or more of the registry keys but I can't be sure of that.
exit devenv
go to below path
hkey_current_user\software\microsoft\visualstudio!
remove 9.0 , 10.0 , 10.0_config (i mean to say all other folders except 11.0 and 11.0_config)
Now start devenv and see the magical colors get back normal
1 - delete all in C:\Users\userNAme\AppData\Roaming\Microsoft\VisualStudio\11.0
2 - open vs console as administrator, and run:
devenv.exe /setup
devenv.exe /ResetSettings1 - delete all in C:\Users\userNAme\AppData\Roaming\Microsoft\VisualStudio\11.0
2 - open vs console as administrator, and run:
devenv.exe /setup
devenv.exe /ResetSettings
This is what helped me...
delete all in C:\Users\userNAme\AppData\Roaming\Microsoft\VisualStudio\11.0
open vs console as administrator, and run:
devenv.exe /setup
devenv.exe /ResetSettings
This solution worked for me. Thanks alot Gaz Winter
If you've installed the preview of Roslyn, unintstall it. This worked for me.
After trying several of the solutions listed here, I eventually found that my issue was caused by a very large (488000+ characters) string variable. Highlighting was working up to that line, but not after it. Once I reduced the length of the string, highlighting in the rest of the file resumed working normally.
I already had VS 2012 Pro installed on my machine. I then installed VS 2013 Pro and started facing this color issue. I then deleted the HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\FontAndColors key and opened VS 2013. This approach solved my issue and the colors were back.
If the windows desktop is configured with a high contrast theme the syntax coloring seems to disappear completely from Visual Studio. If this is the case, select a normal windows theme and set a solid background color (if you don't want a background pictures) to restore syntax coloring in VS.
Problem : Class name and Syntax showing in black color
Solutation:
Step 1: Remove Key :
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\FontAndColors
Step 2: Remove folder :
C:\Users\UserName\AppData\Roaming\Microsoft\VisualStudio\12.0
Step 3: Open command prompt (admin mode) and run below command line :
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE>devenv.exe /setup
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE>devenv.exe /ResetSettings
It work for download this "Productivity Power Tools 2012" and install, after install this tool get this steps go to Tools -> Options -> Productivity Power Tools and turn off the "Colorized Parameter Help" option.
This fixed the keyword as syntax ActionResult is not set for default black color and highlight problem resolved.
I was using Visual Studio 2010 Express for a project and recently changed over to ultimate 2010. I am noticing that when I would debug in express I could put a break point, edit the code if needed and continue without having to recompile.
With VS 2010 ultimate it tells me the version has changed and i have to stop and restart. How do i get the functionality that express had in ultimate?
Thanks for the help.
EDIT: More specifically, here is the message i get:
"This source file has changed. It no longer matches the versio nof the file used to build the application being debugged".
You have to enable 'Edit & Continue' both in the debug menu (should be on by default. check by going to debug > options+settings) and possibly again in the specific project if it's a web project of some sort. It should be a checkbox there.
edit: it's been a bit since i've tried it, but as far as i recall, that's the how. i'll see if i can grab you a link.