My toolbox icons seem to be missing, in addition it shows the "pointer" on every freaking category. It happened when I was trying to add a new category for my obout controls, however I used the 3.5 and 2.0 version and perhaps it caused some conflict. I reset the toolbar but the screenshot is what came up.
I did this in the command prompt:
devenv /resetskippkgs
It restored my toolbox settings! They were all gone before that.
Related
Until quite recently it was possible to click on a method in the VS 2013 Solution Explorer and have the method appear in the code window. That does not appear to be working anymore. Any idea of how to enable this functionality? It was quite useful. For example, in the Solution Explorer view below, clicking on either addBlanks or formatSql would move the code window to the method in question.
It turns out that I have more information about this problem. I completely uninstalled VS 2013 Pro and reinstalled it. Somewhat predictably the problem went away... However, I was getting an error message about the NuGet package manager not being properly installed. To fix this I removed and reinstalled the NuGet package manager. That did resolve the NuGet error message, but the problem with clicking on methods in the Solution Explorer came back. Finally I removed and reinstalled VS 2013 Pro yet another time and now clicking on methods in the Solution Explorer works correctly.
Somehow the original problem reflects some combination of VS 2013 Pro, NuGet, etc.
It is still possible to quickly display a source code file. I am using Visual Studio 2013 Express Update 3.
It might make a difference to highlight/activate the right-most code preview symbol in the Solution Explorer panel:
It is located to the right of the properties screw-wrench symbol.
If this symbol is active, a single click on a file name is sufficient to get the file displayed in the code view. The same applies to methods. Double-click also works, when the preview symbol is not highlighted.
This turned out to be a bug in Visual Studio 2013 Pro Update 3 (and perhaps other versions). Microsoft recognized this bug and has fixed it in VS 2013 Pro Update 4. See https://connect.microsoft.com/VisualStudio/feedback/details/1001072/double-click-in-visual-studio-2013-update-3-solution-explorer-not-working for a discussion and Microsoft's resolution.
Just installed Visual Studio 2013 (it seems there was no choice - tried to download vs 2012 from Microsoft but they automatically redirect me to 2013...).
I noticed that all those things that used to be colored in turquoise - like classes, types, attributes - are now plain black! I mean all those things that trigger the little blue "smart tag" thingie that when you press ctrl+dot you get a little option to add the appropriate "using" statement.
I've looked through and through in the tools > options > fonts and colors. In vs 2012, under "display items", there were entries such as "user types - XXXXX" which were colored turquoise. But in 2013 they're gone too! :-(
Productivity power tools is not installed...
Anyone?
For others who run into this, where the accepted answer doesn't work: try closing your project and deleting your suo file.
I tried devenv.exe /setup (as an admin, in a VS command prompt), I tried changing and restoring themes, I tried rebooting, etc. Nothing worked, but deleting my suo file fixed it.
I had the same issue in VS2013, fixed that with devenv.exe /setup
See
How can I get user type C# syntax highlighting working again in VS 2012 RC?
If you've installed the preview of Roslyn, unintstall it. This worked for me.
Disabling and then enabling Productivity Power Tools 2013 extension resolved the issue for me.
I'm running Visual Studio 2012, when I add a new File/Reference to a project the message box appears showing the error message
set property 'system.windows.resourcedictionary.deferrablecontent' threw an exception
I read an MSDN article suggesting to run the command devenv /resetuserdata on visual studio command prompt to resolve this problem, tried it but didn't work for me. In fact the command prompt shows the Unknown Error message.
Some addins cause this issue for me so have had to workaround it whenever it occurs:
In Vis studio -
Tools > Options > Environment > Add-in Security, uncheck 'Allow Add-in components to load', OK
Restart vis studio
The error shouldn't occur anymore, so go back to
Tools > Options > Environment > Add-in Security and re-check Allow Add-in components to load, OK
To be specific, I get this error when trying to add files to projects and manage Nuget Packages.
Update
I now make a point of opening
'Tools > Nuget package manager > Manage nuget packages for solution'
whenever I open up a new instance of Vis studio, before loading a solution, just to make sure the window loads properly
That way I know I won't get this issue.
In my case it was a style with the same key defined twice in a ResourceDictionary (WPF)
I have Windows azure tools for Microsoft VisulStudio 2013- v2.2 and Windows azure tools for Microsoft lightswitch VisulStudio 2013- v2.2.
I uninstall only Windows azure tools for microsoft lightswitch vs 2013 .
It's working fine...
I fixed it. The resolution was to remove the Windows Azure Tools for Visual Studio 2012 which I was not actually using, and the error went straight away.
In my case it was to first launch Visual Studio in safe mode. You can create a shortcut for visual studio with a target like this:
'"F:\Program Files\Visual Studio\VS2013\Common7\IDE\devenv.exe" -safemode'
Once launched in safe mode, you can remove the problematic extension via the Addin Manager. However, this wont work for some extensions, as the uninstall option might be disabled for certain extensions when running in safe mode, particularly if you have already uninstalled another extension in the same session.
In My case the problem was caused by Paradox Game engine, in which I had uninstalled it via 'Programs and Features' - which in return did not remove the extension which was originally installed via Nuget package. Uninstalling Paradox via "Programs And Features" left the extension itself still registered in Visual Studio, presumably causing a hidden NullReferenceException.
This issue can be caused by any extension that may have an error in it, or by extensions that were not properly uninstalled.
Also, see this article...
The mentioned issue can be resolved by simply restart the Visual Studio. :P
Also seem to be able to get around this by closing the project and vis studio instance, re-opening, then when the start page/open project screen appears selecting Tools > Extensions and Updates..., then pressing Close
Now open the project and the error doesn't get thrown when trying add files or manage nuget packages, weird.
Just annoying you have to remember to open Extensions and Updates each time...
Other wise make sure given Resourcedictionary.xaml path is correct or not
I had to remove Xamarin from Add/Remove Programs in Control panel and restart Visual studio to fix this.
I had this problem with My Devexpress Project in VS 2015
What finally worked for me was.
Close my solution,
Close Visual Studio,
Open Visual Studio,
Create a New dummy project,
Add a form to it,
Close and save the new project,
Reopen original project and all was ok.
for everyone else who are working in silverlight sdk environment with windows phone8 sdk.
The versions of sliverlight which are compatible with visual studio versions -
vs2012- sliverlight sdk 4
vs2013- silverlight sdk 5
I was integrating in vs2013 and as soon as I updated it with silverlight sdk 5, The errors went away.
In my case it was the Line Endings: you can have different formatting and by copy pasting some code one file got a different Line Ending. It was enough to File > Save As and then click the little arrow next to the save button.
Then click on save with encoding and choose the one you are using in all other files.
See Andrew Truckle's answer.
I hope this helps
I am having an issue with my context menu in Visual Studio 2010 that is driving me nuts. I think it started when I installed the Code Snippet Designer Extent ion but I am not 100% sure about that. I didn't notice it until after I uninstalled that extension with a few others.
I have tried reinstalling and then uninstalling the extension again but that didn't work either. I am left with these extensions on my machine DevExpress Tools, Dpack, PowerCommands for VS, Productivity Power Tools and the VS10x Code Marker.
I have another system that has all the same extensions installed but doesn't have the context menu problem and I never loaded the Snippet Designer on that machine, which is why I think the problem was caused by something in that particular extension.
Here is what it looks like.
http://www.mydatafish.com/contextmenu.png I tried to post a picture but I need more points to do so and it is hard to explain without a picture so please take a look at the link.
Anybody have any ideas of how I can remove these phantom mene items? By the way I did try resetting the context mene through the the customize menu item in the Tools menu.
OK I am not sure how it got in the condition that it was but I found the program that was causing the problem. It was something called "Code Helper" and it was an add it that I used with VS 2005. It was listed as a AddIn for Visual Studio 2010 but wasn't inside the Addin directory for 2010.
To get rid of the problem I removed the program from the Programs and Features (Add/Remove).
I have a blank property window that I can not get rid of in Visual Studio 2008 SP1. I have tried every thing to get rid of it.
If I close it it shows right back up after going into debug mode or restarting visual studio. I have tried every thing to fix all the way to reinstalling VS with no luck.
Does any one have a solution for this?
Use the following fix:
Close all instances of Visual Studio Navigate to the following directory (I am using 2008 – for a different version change the 9.0 to reflect the correct version number/folder)
"%userprofile%\Local Settings\Application Data\Microsoft\VisualStudio\9.0".
You should see four files:
toolbox.tbd
toolbox_reset.tbd
toolboxIndex.tbd
toolboxIndex_reset.tbd
Move these files to another folder (or, if you are very brave, delete them altogether. Note, this is very much a case of “Worked on my (colleague’s) PC” – do this at your own risk. Restart Visual Studio and hey presto, your Toolbox should be back to where it needs to be. The user in question did not have any custom items in his toolbox so I can only assume that the fix reverted the toolbox to the original Visual Studio state.
Click Window, Reset Window Layouts.
If that doesn't help, click Tools, Import and Export Settings, Reset all settings. (But backup your current settings)
One thing to try is via the Visual Studio 2008 command line you can run the following command.
devenv /resetsettings
This will restore to factory settings, this could clear up the issue, re-install wouldn't do this for you.