In a Visual Studio Enterprise 2015 Web Performance and Load Test Project, I have lost the ability to add a Load Test. The option is usually right below Unit Test...
Instructions to create a Load Test:
https://www.visualstudio.com/en-us/docs/test/performance-testing/run-performance-tests-app-before-release#create-a-load-test
I found the solution in vs 2017 installer. Apparently not all parts are installed. If you want to install web performance test template project:
run vs 2017 installer
go to Individual components -> Debugging & testing
select Web performance and load testing tools
Repairing Visual Studio solved the problem. I am not sure what caused it in the first place
Related
serviceHub.Host.CLR.x86 taking a lot of memory and CPC in my Visual Studio 2017 solution.
This causes Visual Studio to crash.
Any ideas on what the underlying cause is?
The serviceHub.Host.CLR.x86 is responsible for running some processes in the background for Visual Studio 2017/2019.
Among other features, there are three Visual Studio features that run under this process and, in some cases, cause high CPU/Memory usage. They are:
Full solution analysis.
Live Unit Testing. (only in Visual Studio Enterprise)
Code Lens. (only in Visual Studio Enterprise and Professional)
Disable these features as follows:
Full solution analysis: from Tools\Options\Text Editor\C#\Advanced (please see the remarks section if your Visual Studio 19 version is 16.5 or later)
Live Unit Testing: from Test\Live Unit Test
If the Live Unit Test is running, select Stop.
Go to Tools\Options\Live Unit Testing and disable the option Start unit Testing on solution load.
Code Lens: from Tools\Options\Text Editor\All Languages\CodeLens
This feature has a lot of options. If you like Code Lens and want to keep using it, you can enable/disable each option to check which one is stressing your computer CPU/Memory.
That's it. I hope it helps.
Remarks:
In Visual Studio 2019 version 16.5, Microsoft removed the option to disable the full solution analysis.
However, you still have the option to narrow down the analysis scope to only one document. Select the option Current Document to restrict the analysis to the current document.
This process is also executed when installing Visual Studio with the option "Install and Download" at the same time.
If the computer is not so powerful, it will consume the rest of the CPU power till gets to 100%
Whenever I update WCF service reference in front end project, the service reference update happens and the bottom left corner of Visual Studio indicates that the service reference update is complete, but Visual Studio becomes non responsive after the update. If I close the Visual studio using the Task manager and restart it, reopen the solution, I can proceed as normal and can use the updated service reference. For now I always restart my Visual studio and reopen my solution to continue working on my tasks. Has anyone faced this issue? If anyone found the solution for this issue, could you please help me fixing this as it is very annoying to restart the Visual studio every time I update the service references. Thank you.
(I am using Visual Studio 2013 - project uses .Net Framework, asp.net webforms, and C# as the language for development. - if it helps.)
After trying different options, I guess the size of sln file and the size of references caused the issue for me. We use Resharper in our company which adds extra load when updating the service references.
My Visual Studio doesn't hang/becomes not responsive (most of the times), when i do the following..
1) Go to Tools -> Options -> Source Control - change the default option from Microsoft Git Provider to None.
2) Tools -> Options -> Resharper Ultimate and disabl it.
3) Try to figure out which projects in the solution is not required or affected and unload them.
Then update the reference. Still sometimes it doesn't work for me, but most of the times i dont have to restart the solution using task manager. I always disable resharper before I have to update the service reference and enable it back again once the service reference is updated. Hope it help others if they face similar situations..
I'm trying to open a TFS Build Process Template (DefaultTemplate.11.1.xaml) file, incorporating an activity from Community TFS Build Extensions. I'm following instractions from here, section Get the custom activities into Visual Studio. I had no problems with that back in the RC version of Visual Studio 2012 but now, after upgrading to the release version, an attempt to open the file ends up in an error:
System.Xaml.XamlException: 'The type ‘InArgument(mtbwa:BuildSettings)’ of property ‘BuildSettings’ could not be resolved.'
TFS itself doesn't seem to have any problems running builds based on this template.
I am able to open the file without the trick, but then of course the custom activities are not displayed properly.
Check this out:
http://blogs.blackmarble.co.uk/blogs/rfennell/post/2012/08/30/Type-InArgument(mtbwaBuildSettings)-of-property-BuildSettings-errors-in-TFS-2012-RTM-builds.aspx
Quote:
"if the Visual Studio class library project you were using to manage the process template editing was targeting .NET 4.5, it needed to be 4.0. Well with Visual Studio 2012 RTM this is no longer the case, in fact it is the other way around."
I don't really think this is a great answer but I don't have enough rep to comment...
Build action on the xaml file is set to None?
I had a similar issue when opening build templates in VS 2012 RTM, but I was able to open the xaml "a little," meaning that I could open it in the workflow designer, but a lot of it was just the error activity. I found some errors to the effect that I should add references which I had not needed before (neither in VS 2010 or VS 11), such as PresentationCore and PresentationFramework. I wish I remembered more detail to pass on to you on this point.
I'm currently investigating my options to run automated tests from within Visual Studio 2008 Professional. I noticed that the MSDN page documenting the integrated funcionality is only available for VS 2008 and VS 2005. This kind of makes me suspcious. Since we are planning to upgrade to VS 2010 I'm wondering whether I will able to continue to use my configurations and knowledge with VS 2010? Does anyone here have made any experience with this?
TIA, Thomas
No need to be nervous, the terminology around the test configuration has merely changed in VS 2010. Most of what you know is the same but resides under different product branding which causes some versioning problems in the documentation.
Most notably, "test configuration" is often referred to as "test settings" under 2010.
Microsoft moved away from silo-ed "Team Test" terminology of VS 2005/2008 to a more holistic big picture known as Microsoft Application Lifetime Management, where testing is an integrated component for delivery of successful applications. Keep in mind that most of the documentation you'll find for testing refers to the Test Manager, which ship with the Ultimate and Test editions of Visual Studio. The Test Manager ties Tests to Use Cases and Requirements and is part of that big picture.
If you're not going down the ALM big picture, the focused view of just running tests hasn't changed much at all, with the exception of some new features like Test Impact which are pretty cool.
The following links may be useful to you, as it sounds like you're interested in how the tests can be used by developers or part of your build process:
Running Automated Tests within Visual Studio
Running Automated Tests from the Command-line
Hope that helps!
Has anyone integrated NUnit with Visual Studio? I'm trying to set up a build pipeline like this one. But, I'm pretty new to .NET and I'm still understanding how things work. There are many resources in the internet on NUnit + VS, and I'm confused.
I'd recommend you to use Resharper.
As some say, "It just works".
Disadvantages/side effects of this choice in your case could be:
1. Resharper is not free;
2. Running unit-tests is minor part of Resharper - it also includes tons of other features, which you maybe do not need for now(but you can disable most of them in setttings).
Free solution is - Visual Nunit 2010 Visual studio extension. Free and does exactly what you want.
UPDATE
How to add NUnit to your project.
I've found this tutorial. Follow it step-by-step, I've found it helpful and complete for .NET novices.
The only difference is that in Running Unit-Tests section for running tests author uses test runner tool that is distributed within NUnit itself, but you can use ReSharper runner as described in JetBrains' docs
I'm using this:
http://visualstudiogallery.msdn.microsoft.com/c8164c71-0836-4471-80ce-633383031099
Which works quite well for me. You can access it within VS2010 from View->Other Windows->Visual NUnit
I used TestDriven until it was no longer free, I used Resharper but felt it slowed down my machine too much, I tried the VisualNUnit extension but it appeared to spawn multiple processes of itself that would keep a hold on some of my DLLs, I added NUnit itself as a command under Visual Studio Tools (and also with a toolbar button and some macros in Visual Studio to start the current test and attach) but that cost some effort to set up and didn't feel smooth enough after being spoiled with tools like TestDriven. Eventually I tried NCrunch... I am hooked ever since, and I have even started to favor it over TestDriven! the next tool on my "NUnit bucket list" will be the NUnit extension for Visual Studio 11.
PS: NCrunch should work on your Visual Studio 2010 and the homepage has a very decent demo video.
First download and install the NUnit
Step 1: Open Visual studio
Step 2: Open your project
Step 3: Select Properties from Solution Explorer
Step 4: Select Debug option in the properties window
step 5: select 'Start external program' under the section 'Start Action'
Step 6: Select the path of the NUnit file
Step 7: Save it.
After that when you debug your project NUnit will open.
Setting up Visual C#2010 Express with NUnit
The original and still quite ok test runner.
Test Driven .net
Used to be free, but now costs a small fee unless you're a student or open source developer.
Visual Studio 2011(BETA) is compatible with 2010 and provides test runners out of the box. Refer to Visual Studio 11 Beta Unit Testing – What’s New and Visual Studio 11 Beta - Unit Testing Plugins List. For continuous integration (CI) server U can use TeamCity and also run those test on the server.