Every now and then, I have seen my CPU usage jump up to close to 100% on all cores, which can slow things down somewhat… This looks really impressive, like I’m working so hard that my machine can’t keep up with my frantic pace. Sadly, this isn’t always the truth! Looking at Task Manager, shows the culprit to beÂ microsoft.alm.shared.remoting.remotecontainer.dll. If you are using VS2013 or later, and are not using the Community edition, you may notice some annotations above your methods and properties… This feature is known asÂ Code Lens, and is one of those things that is really worth getting to know, as it’s a massive time-saver. Quick digression from the main theme of today’s symposium to tell you why it’s so good… By default, there are about five or six code lenses, but as I’ve changed my options to show only one, only that one is visible in the…
Tag: <span>Visual Studio</span>
A quirk I have noticed with Visual Studio (2013 and later) is that sometimes when you break in your code and hover your mouse over a variable, instead of showing you the little pop-up that allows you to examine the variable, you don’t get anything. If you try using the Immediate window to see what the variable holds, you get a really informative message like “Internal error in the expression evaluator” which doesn’t help a lot. This might be a bug in the managed debug engine that ships with Visual Studio. Try turning on Managed Compatibility Mode (which effectively turns it into pre-2013 debug engine), located under Options – Debugging: This fixed it for me. Source:Â http://stackoverflow.com/questions/21854426/get-internal-error-in-the-expression-evaluator-on-add-watch-function-when-tr
Stopping a build If you are working on a Grown-Up Solution, that has lots of projects, and takes days to build (OK, slight exaggeration, but you know the feeling!), you might sometimes want to cancel a build. This usually happens when you’ve just changed something, started a build and then realised you needed to do something else before trying to build. It’s very frustrating sitting there waiting for VS to finish the build, only to tell you in a smarmy voice that the build failed. “Yes, I know the build failed, that’s why I wanted to stop it you condescending computer!” It’s at this point that you feel like smacking it in the face (or monitor), but you don’t, because you are too polite. What you would really like to do is stop the build. Thankfully there are a few ways to do this, presented here in reverse order of…
In case anyone has been hiding under a rock for the last few months (and I can’t say I blame you if you have), Microsoft’s latest stupidity is toÂ ignore decades of usability studies, and have everything on the UI look like it’s shouting at you. In particular, Visual Studio 2012 and later have menu bars that look like this by default… Does the word “Bleah!” spring to mind? Thankfully, this monstrosity is easy to fix, but requires using the registry editor. If you aren’t comfortable mucking around in the registry, then ask an adult to do it for you 🙂 Click the Windows button on your keyboard, and type regedit in the search box. Click the Enter/Return key, or click the RegEdit icon that apepars in the search results. Navigate to the registry keys shown below: For VS2012:Â HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\General\ For VS2013:Â HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\General\ Future versions of Visual Studio will probably follow the same…
I had been having some serious grief with Visual Studioâ€™s unit testing tools. VS was complaining that some tests did not exist, and others called methods that didnâ€™t exist. Both claims were total lies as all methods in question existed, and could be found by using the â€œNavigate toâ€ feature in VS.
I had two basic errors when I tried to run tests. One was of the form “Method TestProject.SystemsRepositoryTest.CreateNewCamera does not exist” when the method did exist. I could right-click the test in the Test Results window and choose â€œOpen testâ€ and it would take me there. However, when trying to run the test, VS claimed it didnâ€™t exist.
The other error I got was of the form “Test method TestProject.SystemsRepositoryTest.GetAllCameras threw exception: System.MissingMethodException: Method not found: ‘System.Collections.ObjectModel.ObservableCollection`1
Thanks to these problems, I have wasted loads of time debugging things that could have been fixed with unit testing. It has been frustrating to say the least!
Well, I finally found the answerâ€¦
I opened the bin/Debug folder in the test project in Windows Explorer and deleted everything in it. I then rebuilt the test project, and my tests ran fine.
For some odd reason, it looks like rebuilding the test project wasn’t actually changing the DLLs in the folder, so it was using old versions, in which the methods didn’t exist. Deleting them all forced VS to grab fresh copies of the referenced DLLs, and rebuild the test project’s DLL.
I donâ€™t know if this is a bug in Visual Studio 2010, but it doesnâ€™t seem to be a feature that I would have added in by choice!