As the title says, the coloring is not working. If I to go tools > options and look for 'Coverage Touched' etc in the list of Fonts and Colors, they don't exist there.
If I run the tests with the option to analyse them for coverage, no colors show up in the editor. I have VS 2012 Premium update 3 installed.
I already:
resetted usersettings
ran in safemode (can't run tests then, so useless)
re-installed VS
rebooted everything
A colleague of mine used the exact same installer/image, and it works for him...
Any ideas anyone?
I resetted Userdata (for the 10th time) and I noticed that by default it migrates the settings from 2010 or something. I now unmarked that checkbox, and the problem is now solved.
I'm not 100% sure if the checkbox was the problem, but thats the only difference I can recall.
Related
I have just upgrade from VS2017 to VS2019 and I have my own colors on classes, enums etc. that I would like to be the same in VS2019. I export all my settings, install all the same extension (for example Viasfora, SemanticColorizer) from VS2017 in VS2019, and then import my settings from VS2017.
I open a .cs file and I see my colortheme and 1sec later the colors change to some standard colors.
I have tried the unchecking the "Use enhanced colors for C# and Basic" under options.
And here´s the kicker, the "code preview side-window" shows the right colors...
Anyone got an idea of what this is and how to solve it?
Regards
Ok, from what I have learned so far is that there are more parameters for color customizations in VS19 and there is some name changes that stops the import.
What I did was installing VS theme editor(VS19ThemeEditor)
Changed a bunch off settings in there.
Then I added SemanticColorizer and ViasFora, then went to Tools-->options-->Enviroment-->Font and colors. Changed alot of things there.
And for fun added ClaudiaIDE
TL;DR
You cant export from VS17 to VS19 and expect colors to be the same, you need to edit them again.
I just installed Visual Studio 2013 Premium and was having a good time playing with it and writing unit tests (using MS unit tests). However, the "Test Lists" window and some other Test related windows suddenly disappeared AND they have disappeared from the menu item
Test->Windows. In fact I remember Test->Windows having 4 items under it and now I only see two: Test Explorer, Code Coverage Results. i stress they WERE present in Visual Studio 2013. Clearly, I hit some key combination that made them disappear or something happened to make them disappear. How do I get Test List back? Please don't see they are under Tests->Windows, because for me, they are not (at least now. they were!)
Anyone else seen this? Any solutions? I tried restarting Visual Studio, rebooting.
Also, previously, under the "Test" menu, there was a Debug->"Test in Context" and a Run->"Test in Context", or something like this. It was very handy. If your cursor was with in some test, you could run just that one. I'm guessing this is related.
For all I know, these features have been "optimized" into the new test-window... a.k.a. they have been removed. Some other unit test related features are also gone (the context menu item for "create unit tests" is gone for example, yet can still be called via the command window)
Personally I think this is Microsoft's way of pushing everybody towards the Team Foundation Server but that's just my two cents.
I just had the same issue. In my case I needed to install the NUnit plugin ("Nunit test adapter"). After restarting the tests came back.
Start Developer Command Prompt:
cd to UnitTest-folder\bin\Debug which contains .dll
enter command: mstest /testcontainer:UnitTestMyTest.dll
(this creates the test-result)
in VS:
menu View / Other Windows / Test Results
manage Test Runs: window Test Runs -> connect to Test Run
browse to test-folder\bin\Debug\TestResults
This question actually is an implicit answer, since I could fix the problem in the meantime for myself. But I wanted to publish my experience, since some other developers might have a similar problems.
The problem:
I am using VS2010 prof SP1 on Windows XP SP3, pure C++ only. (AntiVirus software present).
Since some days Intellisense - which is quite helpful under normal conditions - does not work anymore.
Things tried:
created a new simple console application. -> Intellisense still not working.
resetting VS-Settings by means of Tools/Import & Export Settings/Reset. -> Intellisense still not working
Changes to option settings in Text-Editor/C++/Advanced inclusive logging did not help.
-> Intellisense still not working
There was actually an interesting observation:
Intellisense normally creates a directory 'ipch' in the solution directory to store intermediate files. In my solution folders it disappeared as soon as the solution was opened. When I created a folder 'ipch' and opened the solution Intellisense removed the folder again - strange.
The final fix:
During the last week some new Windows updates were installed. I noticed some other unusual behaviour of my PC as well. After having created an image of my PC, I decided to
uninstall Windows updates from 2013-09-11 (4 packages) and one update from 2013-08-28.
(unfortunately I did not note down the KB-numbers)
AND: out of a sudden Intellisense is working again !
Maybe this report could be helpful for some other persons.
Automatic Updates are now disabled on my PCs.
Confirmed 100%
Microsoft Visual Studio 2010 Version 10.0.30319.1 RTMRel
Microsoft NET framework 4.0.30319 RTMRel
Microsoft Windows XP Professional Version 2002 Service Pack 3
Intellisense stops working after installing KB2876217.
Intellisense is back after removing update.
I had the same problem and also had the idea that one of the Windows Updates is buggy, so I can confirm your report.
I tried to uninstall them one-b<-one and found the "bad guy":
KB2876217 destroys intellisense for VS2010 under XP SP3.
A supported hotfix is available from Microsoft to fix this issue. Check at http://support.microsoft.com/kb/2526044/en-us
Actually, it may not be such a good idea to uninstall update KB2876217. Instead, install Visual Studio SP1 update (if not already installed) and then install update KB2526044. I have tried it before and it does work...
I use ClipX on my computer to keep a clipboard history, and it works just fine. After I upgraded to MSVC2012, however, it no longer picks up any of the copies I do inside Visual Studio. It seems that Visual Studio is somehow catching the CTRL+C before ClipX is, or something? Anyway, I prefer ClipX to MS's implementation, so I was hoping there was some way to just completely disable that functionality
Are you running the latest version of ClipX available? Even though it's labeled "Beta", version 1.0.3.9 works well, and if you're on Win7 x64 there's a 64-bit version available, which is what I run. I'm not running Windows 8 or 8.1 yet so cannot comment on whether it works with those.
I'm running VS2013, and I cannot reproduce your problem exactly, but... I do have a similar problem (and solution):
I run VS as administrator (I change the properties of devenv.exe to always run as admin) for interop with IIS, among other reasons. ClipX still picks up the values from copies/cuts, but when I try to use the ClipX popup list to paste a value other than the current clipboard entry, it doesn't actually paste into Visual Studio. ClipX does move the item to the top of the list, and a second Ctrl+V does then paste the value into VS, but it's very annoying.
The solution is to run ClipX as administrator also. Since running a program as admin at startup/login is only possible through Task Scheduler, this is a bit of a pain to set up, but once I've set it up, ClipX has no problem interacting with VS (or any other program I run as admin).
If you are running VS as admin you could try running ClipX as admin (just right-click it in the Start menu) and see if it fixes your problem. If so, then worry about the Task Scheduler part. If it doesn't fix your problem, then well, it was worth a shot.
What the title says. All options in the "Build" tab are grayed out, and run and debug are grayed out in the "Run" tab. I can fix it by giving mono root, but I'm not too keen on having that as a permanent solution.
I have tried creating a new "Hello world" solution just for testing, tried different project file formats(vs 20xx, mono 1.0), reinstalling mono, installing/uninstalling monodevelop-debugger-gdb...
I've been able to run programs before, no idea what happened.
Using linux mint 12 and monodevelop 2.6
Any other info you might need?
I suggest you upgrade to the latest Monodevelop version (3.04). In past releases there was a little bug that allowed what you describe to happen. In my experience it was project specific, meaning, when happened, happened only in one project, usually the last one I was working on.
In the meantime here is a simple workaround to use when that problem happens:
When that happened to me in the past (using version Monodevelop 2.6 on Ubuntu) I found that if I open, compile and run successfully another project, and then go back to try and compile the problematic project (in which the 'Build' options were greyed out) - the problem is solved and all 'Build' menu options become be available again.
I don't know what the bug was, but as I mentioned above, I did not experience the same bug in Monodevelop 3.04, so I recommend you upgrade.
Hope that helps!